agent_list

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

With no annotations, the description carries the full behavioral burden, but it does disclose that results are paginated and token-free. However, it does not clarify what 'token-free' means alongside the agent_token parameter, nor does it describe read-only safety, sorting, filter combination behavior, or response shape.

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 description is a single, front-loaded sentence with no filler. The key purpose and the pagination/auth traits are stated immediately.

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 six optional parameters, no annotations, and no output schema, the description is too sparse. It names the listed fields but leaves parameter behavior and filtering semantics largely unexplained.

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 0% for six parameters. The description only hints at pagination via limit/offset and possibly token handling via 'token-free', but it adds no meaning for agent_token, client_agent_id, claim_generation, or client_session_id.

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 a specific verb and resource: list named agents, plus activity state and claim counts. It is clearly distinct from siblings like agent_attach, agent_detach, and agent_heartbeat, though it does not explicitly name an alternative.

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 guidance about when to use agent_list versus siblings such as items_claimed, search, overview, or dashboard_info. It also does not state exclusions, prerequisites, or whether filtering by agent_token/client_session_id is preferred in certain cases.

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