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

Annotations already declare readOnlyHint=true and no contradiction exists. The description adds some behavioral content by enumerating the chain entries ('the live one, what's up next by wants, and what filled or closed'), but it does not describe ordering, response shape, or what happens when there are no chains.

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?

At two sentences it is short, but the first sentence is a confusing, informal fragment ('Every product btw has run or queued') that front-loads a domain explanation instead of the tool's action. No space is wasted, but the structure sacrifices clarity.

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 zero-parameter read-only list, the description conveys the general contents and points to the status tool, but it never states explicitly that list_chains returns a list of these chains or how they are represented. The cryptic phrasing leaves an agent to infer the basic behavior.

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 has zero parameters, so the baseline is 4; there is no parameter meaning for the description to add, and the schema fully covers the empty 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?

The description never states a direct verb+resource for list_chains; it opens with the cryptic 'Every product btw has run or queued...' and only implies that this tool returns the run/queued chain. The title supplies the action, but the description itself is vague about what the tool actually produces.

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 gives an explicit routing cue: 'Use status for the live one,' which tells the agent that status is the alternative when only the current live state is needed. It does not, however, explain other alternatives such as get_chain, so it is not a full routing guide.

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