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

The description goes far beyond the annotations by disclosing side effects: it moves the deal to Negotiation, tags it agent_mcp, routes multi-rail calls to the offer engine automatically, requires explicit consent, and states offers are indicative and subject to KYC/KYB. It also warns that the tool never confirms or rejects a target rate, which is critical behavioral context. No contradiction with annotations.

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 long, but the complexity of the tool justifies most of it, and it is front-loaded with the most important rule (single-rail only). Some repetition of 'genuinely single-rail' could be trimmed, but every sentence carries substantive routing or handling guidance.

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 19-parameter conversion tool with no output schema, the description is unusually complete: it covers when to call, when not to call, server enforcement, target-rate logging, consent, KYC/KYB, and even the exact reply to use. It loses a point because it does not describe the normal successful offer response shape or clarify several optional parameters, leaving some reliance on inferred conversation context.

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 only 47%, so the description must compensate. It richly explains target_price, target_note, rails, and consent, but several parameters remain unexplained or only implied: current_rate has no schema description and is only referenced as a unit reference, and optional fields like monthly_volume, vertical, licensed, and regions are left without guidance. The description adds value but does not fully cover the gap.

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 the tool's function: capturing a single-product lead and securing an offer in the Crosswire CRM, or logging a client's target rate. It explicitly distinguishes itself from create_solution_offer and get_indicative_price, so an agent can tell exactly which task this tool performs.

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?

Usage rules are explicit and actionable: use only for a genuinely single-rail ask, never for multi-rail architecture (use create_solution_offer instead), and do not call to answer 'what price would I get' (use get_indicative_price instead). It even covers the target-rate logging flow with clear conditions and constraints.

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