get_blocked_urls

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It implies a read-only list operation via 'Get', but gives no details about pagination, result limits, meaning of 'blocked', permission requirements, or output behavior. This is only a minimal improvement over a tautology.

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 sentence, immediately states the action and object, and contains no filler. It is appropriately sized for a simple tool, even though it could include more guidance.

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 read-only tool with one parameter and an output schema, the description provides a minimally adequate statement of purpose. However, it lacks usage guidance, behavioral details, and differentiation from nearby siblings, so it is not fully complete for an agent deciding how to invoke it.

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 0% description coverage, and the only parameter (site_url) is described solely by its title 'Site Url'. The description's phrase 'for a site' adds minimal context that site_url identifies the target site, but it does not explain expected format, required values, or how the parameter is used to retrieve blocked URLs.

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 states a specific verb ('Get') and resource ('list of blocked URLs') scoped to 'a site', making the tool's core function clear. However, it does not differentiate this from similar siblings like get_deep_link_blocks or get_active_page_preview_blocks, so it falls short of a 5.

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, no exclusions, and no mention of prerequisites or typical scenarios. The only contextual clue is 'for a site', which reflects the required site_url parameter but does not provide real usage direction.

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