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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds substantive context beyond that: the email is what invites businesses, that invitation only happens after the customer clicks the confirm link, and that demo requests send nothing. It stops short of noting the non-idempotent 'resend' behavior or delivery/auth caveats.

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 core action, then the downstream consequence, then the exception. No filler and every clause carries information.

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 two-parameter tool with full schema coverage and no output schema, the description covers the action, precondition, and the notable demo-request exception. The main residual gap is that it never states the workflow dependency on create_request in words, though the schema alludes to it.

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% and both required parameters are documented in the schema, including the create_request provenance and the req_ pattern. The description adds no parameter-level meaning, so the baseline 3 applies.

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 ('Sends or resends the confirmation email for a valid draft request'), which clarifies the ambiguous name 'submit_request' and its 'Send confirm email' title. It does not explicitly contrast itself against siblings like create_request or cancel_request, which is the only gap.

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 a precondition ('for a valid draft request') and a special case ('For a demo request nothing is sent'), which implies usage, but there is no explicit statement of when to call this versus create_request or update_request, or when not to call it. Usage is inferred rather than directed.

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