wordpress_wp_transient_list

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

No annotations are provided, so the description carries full disclosure burden. It successfully discloses the hard 100-item limit and describes the output format ('transient keys with expiration times'). However, it fails to explicitly confirm this is a safe, non-destructive read operation or mention any performance considerations when querying the database.

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 efficient sentences with information front-loaded. The '[UNIFIED]' prefix is minor noise that doesn't aid the agent, but the rest of the description is well-structured without tautology.

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?

Adequate for a simple listing tool: it describes the implied return values (keys, expiration times) and pagination limits to compensate for the missing output schema. However, the lack of any parameter documentation for the required 'site' field leaves a critical gap for invocation.

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 has 0% description coverage for the required 'site' parameter, and the description adds zero information about what this parameter represents (site URL, ID, slug?), expected format, or how to obtain a valid value. For a single-parameter tool, this is a significant documentation gap.

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?

Clear verb ('List') + resource ('transients') + scope ('limited to first 100'). Implicitly distinguishes from sibling 'wordpress_wp_transient_delete_all' by describing a read-only listing operation rather than deletion, though it doesn't explicitly name the alternative.

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?

Provides usage context ('Useful for debugging caching issues') suggesting when to use the tool. However, it lacks explicit guidance on when NOT to use it or explicit reference to the delete_all sibling as the alternative for removal operations.

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