get_deal

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

No annotations are provided, so the description carries the burden. 'Get' implies a safe read and the Sales-module prerequisite is genuine behavioral context, but nothing is said about behavior for unknown/unauthorized IDs or access scoping.

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 sentence, front-loaded with the verb and resource, with the field list and prerequisite appended — no filler.

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?

With a single documented parameter and no output schema, the description usefully names the fields returned and the module prerequisite. It stops short of error/not-found behavior, but is otherwise adequate for a trivial read tool.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents deal_id fully ('The CRM deal ID to retrieve'). The description's 'by ID' adds no syntax or format detail beyond the schema; baseline 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?

States a specific verb (get), resource (CRM deal), scope (single, by ID), and enumerates the returned detail (value, stage, pipeline, linked lead/customer). The 'single ... by ID' framing cleanly distinguishes it from the sibling search_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 prerequisite 'Requires the Sales module' is useful, and 'by ID' implies the caller must already hold an ID. But it never states when to prefer this over search_deals or what to do if only a name is known, so usage is only implied.

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