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

The annotations already declare the tool read-only, but the description adds crucial behavioral context by explaining *why* this behavior exists ('Through Royally: its server marks it read-only'), which provides operational context to the agent.

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 definition is brief and front-loaded. The first sentence covers what the tool does and what it returns, while the second provides high-level usage guidance in a highly efficient manner.

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?

Given that there is no output schema, the description provides all necessary information an agent needs: what the tool is, what it returns, and the operational safety profile.

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 coverage is 100%, so the baseline for semantic value is already met. The description primarily focuses on the tool's output and operational context rather than elaborating on the parameters themselves beyond the schema descriptions.

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 that the tool 'Lists registered block patterns' and specifies the data returned (name, title, categories, description). It distinguishes itself by explicitly linking the tool to 'Elementor' through the Royally ecosystem.

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?

It provides clear usage context by explaining the next logical step for the discovered patterns: 'Use insert-pattern to drop one into a post.' This effectively guides the agent on the sequence of operations.

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