get_deal_summary

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

With no annotations provided, the description carries the full burden. It discloses the comprehensive set of returned data (activities, notes, movement history, etc.), giving the agent clear expectations. It does not discuss side effects or limitations, but the read-only nature is implied by 'analisar' and the context is adequate.

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 concise, front-loading the purpose ('PREFERENCIAL para analisar deals') and then efficiently listing the returned components. Every sentence adds value with no 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?

Given the tool has only one parameter and no output schema, the description sufficiently explains what the tool returns (deal data, custom fields, linked person, activities, notes, movement history). It does not detail the output structure, but the listed items provide enough context for an agent to understand the tool's capability.

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 only parameter, deal_id, has 100% schema description coverage as 'ID do negócio'. The description adds no additional meaning or usage details beyond the schema, so the baseline score of 3 is appropriate.

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 it returns a complete view of a deal in a single call, listing specific data points (deal data, custom fields, linked person, activities, notes, movement history). This distinguishes it from sibling tools like get_deal or list_deal_activities, which return partial data.

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 explicitly says 'Sempre usar este tool ao analisar um negócio' (Always use this tool when analyzing a deal), providing a strong usage directive. It implies this tool is preferred for analysis over more specific tools, though it does not explicitly mention when not to use it.

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