Get Blocklist

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

With no annotations, the description bears full responsibility for behavioral disclosure. The phrase 'Return blocklist records' is too vague; it does not indicate whether the tool is read-only, what effects it has, authentication requirements, rate limits, or any side effects. This is a critical gap.

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, which is concise, but it sacrifices completeness. Every part of the description should earn its place; here, it is too brief to convey necessary information, resulting in under-specification rather than proper conciseness.

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 complexity of 11 parameters and the absence of annotations and output schema, the description is woefully incomplete. It fails to explain what the tool does with the parameters, what the output looks like, or how to use it effectively. The sibling list provides no differentiation. This description is insufficient for an agent to correctly invoke the tool.

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 description must compensate. However, the description does not mention any parameters or their meanings. Although parameter names like 'app', 'page', 'limit' are somewhat self-explanatory, others like 'cursor', 'fields', 'groupBy' are not explained. This provides minimal semantic help.

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 says 'Return blocklist records,' which clearly states the verb and resource. However, it does not distinguish the tool from many sibling 'get' tools like get_history or get_failed_history, and it does not specify the context or scope (e.g., which app). This is minimally clear but lacks differentiation.

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. It does not mention filtering, pagination, required parameters, or typical use cases. Without explicit context, an agent cannot determine when this tool is appropriate.

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