agy_list_agents

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

No annotations are supplied, so the description carries the whole burden, yet it never says whether results are cached, how stale the list can get, or what `refresh_models` does behaviorally. It does flag the discovery-only nature implicitly by naming the consuming tool, but the mutating/caching behavior of the single parameter is left entirely opaque.

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?

Two short, front-loaded sentences with no filler; the model-slug note is a genuinely needed caveat rather than padding. Slight loss for the line break making the second sentence read like a continuation of the first rather than a distinct point.

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?

An output schema exists, so the return payload needs no explanation, and the tool is a simple zero-required-param listing call. The one remaining gap that matters, the meaning of `refresh_models`, is unaddressed, which leaves the definition adequate but not 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?

Schema description coverage is 0% and the only parameter, `refresh_models`, is never mentioned in the description, so the agent must guess whether toggling it forces a remote fetch. The effort-level guidance adds useful meaning but describes downstream slug usage rather than this tool's input.

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?

States a specific verb+resource ('List AGY agents') and also names the second payload (model slugs AGY offers), tying itself to the sibling that consumes agents (agy_start). An agent can distinguish this discovery tool from the action tools (agy_start, agy_say, agy_wait) without opening any schema.

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?

Gives an explicit instruction to always read the list here rather than assume a fixed set, and explains how the returned model slugs should be passed downstream (full slug, or base slug plus `effort`). It stops short of stating when not to call it or when a refresh is warranted.

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