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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: the exact return shape, what 'writable' means for each provider, that AIOSEO's table is not written, the edit_posts requirement, and that the call is forwarded to a single connected site.

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?

Purpose is front-loaded, then return shape, then the writable caveat, then permissions and routing. Every clause carries information an agent would otherwise lack; there is no padding.

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?

There is no output schema, so the description carries the burden of explaining return values – and it does, in detail. For a zero-argument, read-only probe with full annotation coverage, nothing an agent needs to invoke it correctly is missing.

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?

The tool takes zero arguments, so the baseline is 4. The description also explicitly confirms it 'takes no arguments,' which is all that is needed.

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 (detect) and resource (active SEO plugin), names the exact providers checked and the resolution order, and makes clear it is a single-result probe. This distinguishes it cleanly from wp_seo_get and wp_seo_set.

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?

Routes the agent to the sibling that supplies post-level fields ('The fields of one post come from wp_seo_get') and states the required capability. It does not explicitly say when not to use this tool, but the sequencing context against wp_seo_get is clear.

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