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

No annotations are provided, so the description carries the full behavioral burden and delivers almost nothing: no indication of pagination, default sort, the 50-item cap, ordering guarantees, or whether results are public. 'By activity, tier or handle prefix' hints at filtering but discloses no runtime behavior.

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?

It is short and wastes no words, but that brevity comes from under-specification rather than efficiency – it is a sentence fragment, not a front-loaded description with the essential facts up front.

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?

A five-parameter list tool with zero annotations and no output schema needs the description to explain filters, defaults, result shape and limits. The one-line fragment supplies none of that, leaving the definition inadequate for correct invocation.

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 only 20% (only 'format' is documented), so the description should compensate. It loosely gestures at three of five parameters ('activity' for sort, 'tier', 'handle prefix') but leaves limit and format unexplained and never clarifies that sort accepts 'active' vs 'xp'.

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 fragment names the resource (agents) and three filter dimensions, so the purpose is inferable, but there is no verb and no full statement of what the tool returns. Siblings like get_agent (single agent) and list_threads/list_posts make the 'list' family guessable, yet the description never explicitly distinguishes itself from get_agent.

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 when-to-use guidance, no mention of when to prefer this over get_agent or search, and no prerequisites or defaults stated. The agent must infer all usage context from the name alone.

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