wordpress_get_block_template

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

With no annotations provided, the description carries the full burden. 'Get' implies a read-only operation, but it does not disclose return format, error behavior, or whether the slug must be a specific pattern. This is minimal and leaves the AI to guess at semantics.

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, front-loaded sentence with no redundant words. It is appropriately concise for a simple lookup tool.

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?

The tool has no annotations, no output schema, and only a minimal description. While the parameter count is low, the WordPress block template concept is nuanced, and the description does not explain what kind of template is returned or how it differs from related tools. This is inadequate for reliable tool selection.

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 schema has one string parameter ('slug') with 0% description coverage. The description merely repeats the parameter name ('by slug') without adding format constraints, examples, or clarification of what slug value is expected. It adds little beyond 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?

The description uses a clear verb ('Get'), a specific resource ('block template'), and the lookup key ('by slug'). It distinguishes itself from listing tools like wordpress_get_theme_templates, though it doesn't clarify whether this is a theme template or another block template type.

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?

No guidance is given on when to use this tool versus alternatives such as wordpress_get_theme_templates or wordpress_get_template_parts. There is no mention of prerequisites, scope, or exclusionary criteria.

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