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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds essentially nothing beyond that — no mention of pagination behavior, default page size, or what a returned entry looks like — so it contributes little new behavioral context.

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?

A single short, front-loaded line with zero filler or repetition. It is not padded, though it is so terse that it borders on restating the title rather than informing.

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?

Because an output schema exists and parameter coverage is complete, the description need not explain returns or fields. However, for a list tool sitting among several blocklist-related siblings, the missing disambiguation of when to call this versus check_blocklist leaves a real gap.

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 100%: skip, type, limit, search, and workspace_id are all documented, including the skip/limit multiple rule and the 100 cap. The description adds no parameter meaning on top of the schema, so the baseline of 3 applies.

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 gives a specific verb (Get/List) and resource (blocklist) plus the entry types returned (blocked emails and domains). It does not explicitly distinguish itself from close siblings like check_blocklist, add_to_blocklist, or remove_from_blocklist, so the agent must infer that this is a read of the full list.

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 when-to-use guidance, no exclusions, and no named alternative to check_blocklist (single-value lookup) or get_leads. The agent is left to infer usage purely from the tool name and the sibling list.

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