list_circuits

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

Adds context beyond annotations: authoritative source from installation settings, notes that names may differ due to line wraps. Annotations already cover read-only/idempotent, so description adds provenance.

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?

Three sentences, front-loaded with read-only and list action, then essential nuance. Zero waste.

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-param tool with output schema and strong annotations, the description fully explains purpose, authoritative nature, and relationship to a sibling. 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?

No parameters; schema trivially covers everything. Baseline 4 applies.

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?

Specific verb+resource: lists registered measurement circuits with stable ids and names. Distinguishes from sibling get_circuit_breakdown by noting authoritative naming.

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?

Explicitly states when to prefer this tool (canonical circuit names) and cites get_circuit_breakdown as the alternative with display-derived names. Clear usage context.

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