wordpress_get_theme_templates

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

No annotations are provided, so the description carries the full burden. It only says 'Get' with no mention of response format, pagination, permissions, or specific API behavior. The phrase 'block theme templates' adds a little context but does not disclose what the tool actually does beyond fetching, leaving the agent underinformed about side effects or return value structure.

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 concise sentence that immediately conveys the action and resource. It contains no fluff or redundant information, earning its place perfectly.

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 and a minimal description, the tool leaves the agent guessing about what will be returned (e.g., a list of template names, IDs, or full JSON). Given the large set of sibling tools, the description also fails to clarify how this tool fits into the broader workflow, making it undercomplete for even a simple fetch operation.

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 input schema has zero parameters, so there are no parameter semantics to explain. The baseline for 0 parameters is 4, and the description does not need to add anything. The schema already covers the trivial parameter space completely.

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 resource ('theme templates'), with a qualifier 'block theme templates from WordPress API' that narrows scope. It is clear enough but could be more explicit about what a theme template is in this context and how it differs from related tools like get_template_parts.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools such as wordpress_get_block_template (singular) and wordpress_get_template_parts exist, but the description does not mention them or any exclusion criteria. The agent must rely on the name to infer usage.

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