retrieve_contact_deals_list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds a green 'READ-ONLY' label, HTTP method (GET), and endpoint path, which provide minor additional context beyond annotations. No contradictions.

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 with two clear sentences plus a formatted line for the HTTP method. No filler content, though the emoji and formatting are minimal and acceptable.

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?

The description is adequate for a simple list retrieval tool with a required contact ID. It does not describe the response format or pagination behavior, but these are partially inferable from parameters (limit, offset). No output schema exists to supplement.

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 has 100% description coverage, so the schema already documents all parameters. The tool description does not add any additional parameter-level details beyond what is in 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 clearly states 'Retrieve a list of contact's deals' and 'Fetches data. Makes no changes.' The verb 'retrieve' and resource 'list of contact's deals' are specific, and the tool name includes 'contact_deals_list', distinguishing it from sibling tools like 'list_all_deals' which retrieves all 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 description implies usage for retrieving deals of a specific contact via the required 'id' parameter. However, it does not explicitly state when to use this tool versus alternatives (e.g., 'list_all_deals' for all deals), nor does it mention any exclusions or prerequisites.

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