get_deep_link_blocks

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

No annotations are provided, so the description carries the behavioral burden. It conveys a read-only list operation through 'Get list', but it does not disclose details such as pagination, result limits, how blocking is determined, or whether the list is scoped to the provided site_url.

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 short sentence with no filler, and the operation is front-loaded. It is somewhat under-specified, but the brevity is appropriate for a simple read operation.

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 one-parameter read tool with an output schema, this is almost usable, but ambiguity with siblings like get_blocked_urls and the unexplained 'deep link' terminology leave gaps. It is minimally complete but not robustly contextual.

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% and the description does not explain site_url or its expected format. The property name is self-explanatory to a degree, but the description adds no meaning beyond what the schema minimally implies.

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 operation and resource: 'Get list of blocked deep links.' It is a specific verb and object, but it does not distinguish this from siblings like get_blocked_urls or explain what counts as a deep link, so it is not fully differentiated.

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 context about which site_url values are valid or when blocked deep links would exist. The agent must infer usage entirely from the tool name and parameter.

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