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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds little behavioral context beyond the fact that details are returned; it does not mention possible 404 behavior, field scope, or whether the deal object is fully expanded. With annotations covering side effects, this is adequate but not rich.

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 clear sentence with no unnecessary words or fluff. It is appropriately sized for a simple get-by-id tool, though it is minimal enough that it does not front-load any usage hints or caveats.

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 low complexity, one required parameter, and read-only annotations, the description is minimally viable. However, there is no output schema and no return-format description, and the description does not help the agent choose this over sibling deal-listing tools. A short note about when to use it or what details are returned would make it complete.

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% because the only parameter, id, is documented as 'Deal id or slug.' The description does not add extra parameter meaning beyond what the schema provides, so the 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 states a clear verb and resource: 'Get details of a specific deal.' It conveys that this is a single-item retrieval operation, distinguishing it from list-oriented siblings like get_latest_deals or search_deals. However, it does not explicitly mention lookup by id/slug in the description itself, leaving some differentiation to the schema.

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 guidance is given about when to use this tool versus alternatives such as search_deals or get_deals_by_category. The phrase 'a specific deal' implies the agent should already have a deal identifier, but this is not stated explicitly and no exclusions or alternative-routing advice are provided.

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