getDeal

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention whether the operation is read-only, what happens on missing IDs, or what fields are returned. It essentially restates the tool name with 'by ID', adding no behavioral insight beyond the schema.

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 a single, front-loaded sentence with no redundant words. It is concise but not overly terse to the point of being cryptic, fitting the simple nature of the tool.

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's simplicity, the description is minimally adequate, but it lacks detail about the return format, error behavior, and any required permissions. No output schema exists, so the description could have added more context, but it does not. For a simple get-by-ID, this is a borderline 3.

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 already fully documents the single `id` parameter as 'Deal ID' (100% coverage). The description's 'by ID' merely reiterates the schema, adding no new semantic meaning. Baseline score 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 'Get a deal by ID' clearly specifies a single-entity retrieval operation with verb 'get', resource 'deal', and scope 'by ID'. This distinguishes it from siblings like listDeals (bulk retrieval) and createDeal/updateDeal. The intent is unambiguous.

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?

No usage context is provided. The description does not state when to use this tool instead of listDeals or other getters, nor any prerequisites such as requiring a valid deal ID. This leaves the agent without guidance on tool selection.

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