get_top_blocked

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

The description reveals that results are sorted by query count, which is behavioral detail beyond the tool name. However, it does not disclose pagination, response format details, or any side effects. Since annotations are absent, the description carries full burden but only partially meets it.

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, concise sentence that delivers the essential information without unnecessary words. It is front-loaded and every word earns its place.

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's simplicity (one optional parameter) and the existence of an output schema (which covers return values), the description is nearly complete. It lacks usage context relative to siblings, but otherwise adequately describes the tool's purpose and behavior.

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 0% because the description does not mention the 'count' parameter. The input schema provides the default and type, but the description adds no meaning about its purpose or constraints. For a single-parameter tool, this is a significant gap.

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 'Get top blocked domains by query count', clearly indicating the verb (get), resource (top blocked domains), and sorting criterion (by query count). This distinguishes it from siblings like get_top_permitted and get_top_clients.

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?

No guidance is provided on when to use this tool versus alternatives like get_recent_blocked or get_top_permitted. There is no mention of prerequisites, best practices, or when not to use it.

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