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

Annotations mark this as non-read-only, non-idempotent and non-destructive, and the description adds substance to that: the call creates one persisted test item, is excluded from counts and emails, and returns a pass indication plus affected pages. What it does not say is whether test items accumulate or how to clean them up after repeated calls.

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?

A single dense sentence with the action front-loaded and qualifications trailing. It is slightly run-on but every clause (scope, side effects, return signal) earns its place.

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?

The write-side effects and the shape of the result are conveyed, and an output schema exists to cover return details. However, for a mutation tool whose two required identifiers are completely undocumented, the description leaves a real gap an agent cannot fill from structured data.

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 0% for both required parameters, so the description must carry the burden — but it never mentions 'site' or 'plugin_id' or their expected format (site name vs. domain, plugin slug vs. numeric id). An agent must guess parameter values from the schema alone.

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 and resource (sends one test submission to a form or booking page) plus the outcome (reports success and which published pages carry it). The parenthetical 'not payments; never counted or emailed; kept as a test item' separates it from real-submission siblings like add_booking and add_people.

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 a clear context for use — verify a plugin works and see where it is live — and explicitly excludes payment plugins from scope. It stops short of naming a sibling to use instead (e.g., add_booking for a real submission, update_plugin for configuration), so the alternative path is left implicit.

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