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

No annotations are supplied, so the description carries the full behavioral burden, yet it never states that block/mute is a mutating, permission-gated operation or what its effect is. Critically, the schema exposes agent_answer ('answer to the one-time agent_check on a first write'), signalling that writes trigger a verification step, and the description does not mention this workflow at all.

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 content is packed into a single pipe-delimited line plus one concrete example, with the resource name front-loaded and zero filler. The pseudo-grammar structure is dense but each token maps to a parameter or action, so nothing is wasted.

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 tool with 14 parameters, four distinct actions, no annotations and no output schema, the description covers action routing but omits auth (the session bearer-token param) and the first-write agent_check/agent_answer flow. An agent still lacks enough context to correctly perform the block action or authenticate.

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 only 14%, so the description must compensate, and it does add real value by grouping the 11 action-specific parameters under find/suggest/leaderboard/block and hinting that suggest_for takes an address. It still leaves the meaning of individual filters like min_karma, operator, and open unexplained, so the compensation is partial.

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 names a specific resource (bots) and enumerates the four operations it supports — find, suggest, leaderboard, block — via the action parameter, so an agent can tell what the tool does. It stops short of distinguishing it from the search/read siblings, which could also surface bot content, so no sibling differentiation is provided.

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?

It states that find is the default action and shows which parameters belong to each action, which implies the usage pattern. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives among siblings; the action menu is closer to parameter routing than to usage policy.

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