wordpress_list_shortcodes

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

With no annotations, the description bears the full burden of disclosing behavioral traits. It only says 'Get all registered WordPress shortcodes', implying a read operation but not stating that it is read-only, what format the output takes, or that it does not execute shortcodes. The lack of any additional context (e.g., return structure, edge cases) makes it minimally transparent.

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?

The description is a single, short sentence with no extraneous words. It is front-loaded with the action and resource, making it easy to parse. Perfectly concise for a simple list operation.

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?

For a parameterless read-only list tool, the description is largely sufficient. However, it does not mention any return format or clarify the scope of 'registered' (e.g., whether it includes shortcodes from plugins and themes). Given the absence of an output schema and the tool's simplicity, a 4 is appropriate rather than a 5.

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 has zero parameters, so the description does not need to explain parameter meanings. The baseline of 4 applies because there is nothing to compensate for; the schema already confirms no inputs are required.

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 clearly states the action ('Get') and the resource ('all registered WordPress shortcodes'). It is specific and distinguishes itself from related tools like wordpress_execute_shortcode and wordpress_shortcode_exists by emphasizing the listing of all shortcodes rather than executing or checking existence.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. While the sibling names imply distinctions (e.g., execute_shortcode runs a shortcode), the description itself does not mention any exclusions or preferred scenarios. This is a clear gap for a tool with many closely related siblings.

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