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

Annotations already disclose a non-read-only, open-world, non-idempotent write. The description adds real value beyond that: confidentiality, the intake path, the callback outcome, and the consent precondition. This is solid supplementary context, though it does not state rate limits or what happens to a duplicate submission (consistent with idempotentHint=false).

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 compact sentences with no filler. The core action and consent condition are front-loaded, followed by outcome and exclusion in descending order of importance.

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 9-parameter write with no output schema, the description covers purpose, side effects, the callback outcome, and the consent requirement that gates the call. An agent has enough to invoke correctly, though it does not clarify how this differs procedurally from request_service.

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%, with every parameter documented including requirements and formats, so the schema carries the full burden. The description adds no parameter-level meaning beyond it, making the baseline 3 correct.

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 specific verb and resource ('File a confidential consultation request with the firm') plus the scope constraint ('on behalf of a person who has agreed to it'). It distinguishes itself from the marketing/solicitation use case, but it does not explicitly contrast with the closest sibling, request_service, leaving the agent to infer the boundary.

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?

It gives the operative context ('Goes through the same intake as the website contact form; the firm calls or emails back') and an explicit exclusion ('Not for marketing or solicitation'). However, it does not name the alternative tool to use for non-consultation requests, so the when-to-use routing vs siblings is only partially closed.

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