Send test email

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, openWorldHint=true. The description adds the confirm=true gate and 'changes account state', which is useful supplementary context, but the cryptic 'OAuth integrations require posts' adds little clarity and the destructive side effects are not spelled out.

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 action and immediately followed by the state-change warning and the confirm requirement. Tight and without padding, though 'OAuth integrations require posts' is terse to the point of ambiguity.

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 destructive, non-idempotent mutation with no output schema, the state-change and confirm context is helpful but incomplete: it does not explain what 'account state' is affected, success/return behavior, or the 422 rate-limit implications already hinted at in the schema. Adequate but with clear gaps.

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%, so the schema already documents all seven parameters including recipient_emails, confirm, and payload. The description only echoes the confirm requirement and adds no syntax or format detail beyond the schema, 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 first sentence 'Send test email' restates the title verbatim and gives the resource but no differentiating scope. With many sibling send/email tools (podcasts_send_private_feed_email, preview_post), an agent cannot tell what makes this one distinct or which post/publication it targets from the description alone.

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 states a prerequisite ('requires confirm=true for the user-requested action'), which is real usage guidance, but gives no when-to-use vs when-not guidance and never contrasts with alternatives like preview_post. Usage is implied rather than directed.

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