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

Annotations already declare readOnly=false, idempotent=false and openWorld=true; the description adds value by labeling the operation WRITE and explicitly stating no notifications are sent, which is the kind of side-effect scoping annotations cannot express. It doesn't mention duplicate detection or failure behavior, but for a straightforward create that's a minor gap.

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?

Three short sentences, front-loaded with the WRITE marker and the core action, then dependency pointers. Nothing is wasted and it's scannable at a glance.

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 15 parameters, no output schema, and annotations that don't describe responses, the description never says what a successful create returns (e.g. the new deal id) — an agent would need that to chain follow-up calls like adding notes or marking won. Otherwise the input-side guidance is adequate.

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 80%, so the schema already explains nearly every field including deal_stage and currency guidance. The description's pointers to the stage and currency list tools largely duplicate the schema's 'see revampcrm_list_deals_by_stage' note, adding little new parameter meaning beyond the POST /Deals endpoint detail.

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 and resource ('create a new deal (opportunity)') plus the account scope, and clarifies the optional contact link. It is immediately distinguishable from siblings like revampcrm_update_contact or revampcrm_mark_deal_won.

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?

Explicitly routes the agent to revampcrm_list_deals_by_stage and revampcrm_list_deal_currencies to resolve required/valid values, which is real use-time guidance. It does not, however, say when to create a deal vs. search for an existing duplicate or how to proceed if the deal already exists.

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