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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so 'read-only, runs straight away' is largely repetition. Beyond that the description adds only the SEO-plugin framing; it says nothing about what the returned meta structure looks like or how serialized values are handled.

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 with the core action front-loaded. The parenthetical site hint and the 'Through Royally' branding sentence are partly redundant with the schema enum and annotations, but overall it is tight.

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 no output schema, the description should ideally describe the shape of returned meta (key/value map, serialized arrays) — it does not. Safety profile is covered by annotations and the SEO use case is covered, so it is adequate but leaves a real gap for an agent parsing results.

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 coverage is 67%: 'key' and 'site_id' are documented in the schema, while 'term_id' carries no description. The description adds no parameter-level meaning (e.g., that omitting 'key' returns the full meta set), so it neither compensates for the 'term_id' gap nor extends the schema.

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+resource ('Get term meta data') and clarifies that the terms are tags/categories, which separates it from post-meta and user-meta siblings. It does not explicitly name the adjacent tools (wp_get_term, wp_get_post_meta, wp_get_seo_meta), so differentiation is implied rather than stated.

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?

'Useful for reading tag/category SEO meta stored by Yoast, Rank Math, or AIOSEO before editing it' gives a concrete usage context and a read-before-write workflow cue. No exclusions or named alternative tools are given, which caps it below a 5.

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