Get Deal by ID

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond that — no error behavior for unknown IDs, no statement of what is returned, and no permission or rate-limit context.

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 text is short and front-loaded with no filler, but the first sentence is a verbatim echo of the title and the second only rephrases it. It is concise because it is nearly empty, not because it is efficient.

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 read tool with full schema coverage and rich annotations, the bar is low, but with no output schema the agent has no idea what a deal object contains or what happens when the ID does not resolve. The description should at least sketch the return shape or failure mode.

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?

Schema description coverage is 100% and the single required parameter is documented with type, UUID format, pattern, and description, so the baseline is 3. The description's phrase 'unique identifier' adds no meaning beyond the schema.

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 restates the name and title almost verbatim: 'Get Deal by ID. Retrieves a single deal by its unique identifier.' The only added information is the word 'single', which weakly distinguishes it from list_deals and search_deals, but no sibling is named and no verb or scope beyond the title is stated.

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?

There is no guidance on when to use this tool versus list_deals, search_deals, find_deals_by_email, or list_deals_by_contact. The agent must infer that this is the direct-lookup path when a UUID is already known, which the description never says.

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