get_deal

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

No annotations provided, so description carries full burden. It states the tool retrieves comprehensive information about a deal, including custom fields and related entities, which is helpful. However, it does not disclose any potential behaviors like error handling, rate limits, or authorization requirements.

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 front-loaded with a clear one-line purpose, followed by a detailed paragraph and structured Args/Returns/Examples. It is concise without being overly terse, though the paragraph repeats some words.

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 an output schema exists, the description does not need to detail return structure. It mentions 'JSON object with deal details' and provides an example. The tool is simple (one param), so the description is sufficient for an agent to understand its use.

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 schema has 0% description coverage for the single parameter. The description includes 'Args: deal_id: The Pipedrive deal ID', which adds context beyond the schema's 'Deal Id' title, but does not provide format or constraints beyond what the schema already indicates.

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 'Get a single deal by ID with all details', using specific verb and resource. It distinguishes from sibling tools like 'get_deals' (which lists deals) and 'search_deals' (searching for deals).

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 implies usage when you have a specific deal ID and need full details, but does not explicitly state when not to use it or mention alternatives. The sibling list provides context, but the description itself lacks explicit guidance.

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