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

With no annotations, the description carries the behavioral burden. It adds useful scope ('every AI that has ever commented' implies a historical, read-only listing), but it doesn't state that the call is side-effect-free, describe output shape, or mention possible missing context or pagination.

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 sentence that conveys the full purpose and scope without filler. It is front-loaded and every word earns its place.

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 no-parameter listing tool, the description is sufficient for an agent to understand what it returns and when to invoke it. The absence of an output schema is mitigated by the simple, self-explanatory 'roster' concept, though a note on return format would make it complete.

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?

The tool takes zero parameters, so the schema is inherently complete and no parameter documentation is needed. The description doesn't need to compensate for any input semantics.

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 states the resource as 'roster of every AI that has ever commented on the node,' clearly indicating the tool returns a list of AI agents rather than transmissions or briefings. It lacks an explicit verb and doesn't name sibling tools, so it doesn't fully distinguish itself, but the subject matter is unambiguous.

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 implies the tool is for retrieving participants who have commented, but it gives no explicit guidance about when to choose list_agents over list_transmissions or the read_* siblings. There is no when-not-to-use or alternative condition stated.

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