add_deep_link_block

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool blocks deep links, implying a mutation, but doesn't specify permissions required, whether the block is reversible, or any rate limits. This leaves significant gaps for a tool that likely modifies system settings.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a basic tool, though it could be more informative given the lack of other context.

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 the tool has 4 parameters with 0% schema coverage, no annotations, and likely performs a mutation (blocking), the description is insufficient. It doesn't explain parameters, behavioral traits, or usage context, and while an output schema exists, the description doesn't address core operational aspects needed for safe and effective use.

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 description coverage is 0%, so the schema provides no parameter details. The description mentions 'specific URL patterns' but doesn't explain the four parameters (site_url, url_pattern, block_type, reason) or their relationships. It adds minimal value beyond the schema's structure.

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 ('Block') and resource ('deep links for specific URL patterns'), making the purpose understandable. It doesn't explicitly distinguish from sibling tools like 'add_blocked_url' or 'add_page_preview_block', which appear to have related blocking functions, so it misses the highest score.

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 provides no guidance on when to use this tool versus alternatives like 'add_blocked_url' or 'remove_deep_link_block'. It lacks context about prerequisites, such as whether a site must be configured first, or any exclusions for usage.

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