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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context beyond them: it deduplicates against open requests by adding a vote, it states what is returned, and it sets the expectation that "No date is promised." It does not say what happens on retry beyond the schema's idempotency key, and the vote-matching/merge behavior could use one more sentence.

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?

Front-loaded with the action and return value, then a clean when/not-for block. The opening clause about "asking for something none of the other tools can do" is nearly repeated by the "Use this when" line, a small redundancy, but no sentence is wasted overall.

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 five-parameter write tool with no output schema, the description supplies the return shape, the no-commitment-on-timing caveat, and the routing rule. Remaining gaps are minor: no failure/error behavior and no guidance for the optional `closest_existing_tool` field.

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 coverage is 80%, so the baseline is 3, and the description adds little per-parameter meaning beyond the vote-matching hint. The undocumented `closest_existing_tool` parameter in particular is left without guidance in prose, which is exactly the field an agent would fill inconsistently.

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 concrete verb+resource ("Files a request with MTD Chase") and immediately delimits it against all siblings: it is for capabilities "none of the other tools can do." It also covers the second mode ("adds a vote to a matching open request") and the return payload (ID, status, workaround), so an agent can place it precisely among the 19 siblings.

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?

Gives an explicit positive trigger ("Use this when: the practitioner wants a capability MTD Chase doesn't have") and an explicit exclusion ("Not for: reporting a single Client's problem"), which is the split an agent would otherwise get wrong versus client-level tools. It also names the alternative path implicitly by routing unmatched capabilities here instead of to another tool.

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