List chord vocabulary

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

No annotations are present, but the description only explains what is listed and does not disclose any behavioral traits such as read-only nature, authentication needs, or rate limits. The 'list' action implicitly suggests no side effects, but this is not explicit.

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 two sentences, front-loads the action ('List...'), and provides an illustrative example without unnecessary words.

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?

Given the tool has no parameters and no output schema, the description is reasonably complete, specifying what is listed. However, it does not detail the output structure (e.g., list of strings vs objects), but the context signals (0 param, no nested objects) suggest simplicity.

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, and the description does not need to explain inputs. The baseline for 0 parameters is 4, and the description adds value by explaining the output format.

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 clearly states the tool lists chord roots, qualities, time signatures, and key signatures used by iReal Pro, and provides an example of chord notation. It distinguishes from siblings like list_styles and list_charts.

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 usage before generating charts with 'so generated charts use valid symbols', but it does not explicitly state when to use vs alternatives or provide exclusions.

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