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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the REST endpoint but no additional behavioral context such as error handling, response format, or rate limits. It is consistent with annotations but does not enrich beyond them.

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?

A single, front-loaded sentence that directly states the purpose and includes the REST endpoint. Every word earns its place, with no fluff or redundancy.

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?

For a simple get-by-ID operation with a well-documented parameter and read-only annotation, the description is largely adequate. It lacks explicit mention of the response, but the absence of an output schema and the simplicity of the operation make this acceptable. A 4 reflects that it is complete for practical use, though not exhaustive.

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 fully covers the only parameter (id) with a description, so schema description coverage is 100%. The description's mention of 'by its id' adds no new meaning beyond what the schema already provides. Baseline of 3 applies.

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 action ('Get') and the resource ('a single deal by its id'), with specificity that distinguishes it from sibling tools like pipedrive_list_deals and pipedrive_search_deals. The REST endpoint further reinforces the precise operation.

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?

Usage is implied by 'by its id'—the agent must have a deal ID. However, there is no explicit guidance on when to use this versus listing or searching deals, nor any exclusions or alternatives mentioned. The description relies on the tool name and context.

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