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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the shape of the returned explanation content, with no note on how AuditMe-specific check wording is versioned or scoped.

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?

One sentence, front-loaded with the verb and resource, and the four returned sub-sections are packed into a compact list with no filler.

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?

With an output schema present and annotations covering the read-only/idempotent profile, the definition only needs to frame purpose and content. It is nearly complete; the sole gap is guidance on when to choose this over get_audit_methodology.

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 the single enum parameter is fully documented in the schema, so the schema does the heavy lifting. The description adds no syntax, default, or selection guidance for the seven enum values, matching the baseline 3 expected at high coverage.

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 pairs a specific verb ("Get explanation") with a specific resource ("an SEO concept") and even enumerates the sub-sections returned (definition, why it matters, how AuditMe checks it, best practices). It does not, however, distinguish itself from the similarly explanatory sibling get_audit_methodology, so an agent must still infer the boundary.

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?

Usage is only implied: the content breakdown (definition, rationale, checks, best practices) suggests calling it when a user needs an SEO concept explained. There is no explicit "use this when / not when" clause and no alternative tool is named, even though get_audit_methodology and seo_audit overlap in explanatory territory.

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