pipedrive_get_project_changelog

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the description is not burdened with safety disclosure. The description adds context about pagination (cursor, limit), return fields (actor_user_id, new_values, old_values), and the 'public beta' status, which are valuable beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary purpose and output details. Every sentence provides essential context: the first sentence defines the action and result, the second adds pagination and beta status. No redundant or extraneous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description compensates by specifying return fields and pagination details. The context of public beta and add-on requirement is included. However, the exact pagination structure (e.g., next cursor behavior) is not fully detailed, leaving minor gaps for implementation understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers all three parameters (id, cursor, limit) with descriptions, so baseline is 3. The description does not add additional parameter documentation beyond what the schema provides, though it does mention pagination which relates to cursor and limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'changelog for a project', specifying what is returned (changed, when, by whom) and the field structure (actor_user_id, new_values, old_values). It distinguishes from sibling tools like pipedrive_get_project by focusing on changelog rather than current state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria. However, the purpose is clear from the name and description, and the pagination details (cursor, limit) imply usage for large datasets. Sibling tools like pipedrive_get_project are distinct in functionality.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.