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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the return field set and a version prerequisite for plugin-connected sites (Xyle Connector v0.2.2+). It does not describe pagination or failure behavior, keeping it below 5.

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?

Two tight sentences with the reuse rationale and return shape front-loaded, followed by the compatibility prerequisite. No filler and nothing misplaced.

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 usefully enumerates the returned fields and notes the verbosity option, which is enough for an agent to call it confidently. Minor gaps remain around ordering/count semantics of the 'recent' list, but the essentials are present.

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 all three parameters (site_id, limit, detail) are fully documented in the schema. The description adds no parameter syntax or format meaning beyond that, 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?

States a specific verb (List), resource (recent images in the site's WordPress media library), and the underlying goal (reuse an existing image instead of re-uploading). It even enumerates return fields (id, url, title, alt, dimensions), so an agent can distinguish it from wp_upload_image without opening any schema.

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 clear intent-based guidance: use this to REUSE an existing image instead of re-uploading, which implicitly routes the agent away from wp_upload_image. It names no explicit alternative tool or exclusion, so it falls short of the top tier.

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