wordpress_get_block_patterns

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It merely restates that it gets all available block patterns without detailing what 'available' means (e.g., from themes, plugins, or block directory), return format, pagination, or any authentication requirements. This is minimal disclosure beyond the basic operation.

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, clear sentence that is front-loaded with the verb and resource. Every word contributes to the meaning, and there is no redundant or vague text.

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 simple no-parameter retrieval tool, the description is adequate but not fully complete. It does not explain what qualifies as 'available', the return structure (especially given no output schema), or any caveats, leaving some ambiguity for an agent deciding selection and 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?

The tool has zero parameters, and the schema has no properties, so the description does not need to clarify parameter meanings. Baseline for zero parameters is 4, and the description adds no conflicting information.

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 specific verb 'Get' and a specific resource 'block patterns', clearly indicating the operation of retrieving all available block patterns. This distinguishes it from sibling tools like 'get_block_types' or 'get_reusable_blocks' based on the unique resource name.

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 implies that you should use this tool when you need to retrieve all block patterns, but it does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or prerequisites. There is no comparative guidance despite many related block tools existing.

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