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

Adds substantial context beyond the annotations: the catalogue and prices come from the live page, never from memory; a human replies by email; nothing is quoted, charged or scheduled; and the agent must not claim success unless the returned status is 'filed'. The only mild tension is destructiveHint=true versus 'nothing is charged', but that reflects a real external side-effect (a person is dispatched), not a contradiction.

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 two invocation modes, then constraints, then two concrete example utterances; every sentence carries operational content. It runs long for a four-parameter tool, but the length is justified by the real-world side effects being governed.

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 an open-world, non-idempotent tool with a full schema and an output schema, the description covers what an agent needs: how to discover engagements, what each argument must contain, the human-reply flow, and the status check that gates any success claim. Return-value detail is rightly left to the output schema.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: `engagement` must be an id taken from this tool's own empty-call listing, `who` determines which records the person pulls, and email/detail must be passed verbatim rather than normalized.

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+resource: files an engagement enquiry so a person at Brick & Mortar performs a paid read of the public record. It also distinguishes the two modes of the tool (empty call lists engagements and prices; populated call files the enquiry), so an agent can tell it apart from the free research 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?

Explicit when-to-use ('only after the free tools have been tried or when the person asks for someone to do the work'), a precondition ('confirm with them what will be sent'), and a hard reporting rule (

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