list_blocked

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

No annotations provided, so description must fully disclose behavior. Only says 'list users,' omitting details on pagination, ordering, rate limits, or whether it returns full user objects. Insufficient for a list operation.

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?

Single sentence is concise but overly short, sacrificing useful detail. Front-loaded with purpose but lacks supporting context. Every word earns its place, but more content is needed.

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?

Output schema exists (true) but description does not reference return format. With no annotations, the description is too minimal for a list tool. Missing details on pagination, default limit, and result structure.

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% (no description in schema), and description does not mention the 'limit' parameter. It adds no meaning beyond what the schema type and default provide.

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?

Description clearly states the tool lists users in the blacklist, which is a specific verb+resource. It distinguishes from siblings like block_user (blocking) and list_contacts (contacts). However, it lacks additional context like scope (e.g., all chats or specific).

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 on when to use this tool versus alternatives. It is implied for viewing blocked users, but no explicit when/when-not or comparison with sibling tools like get_participants or list_contacts.

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