List Mathter skills

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and remote-source aspects. The description adds meaningful context beyond that: it is a 'live list, straight from mathter.ca,' implying results may change and reflect current server state rather than a static catalog. It stops short of describing pagination or return format, so not a full 5.

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 tight sentences with zero waste. The core purpose is front-loaded and the actionable routing advice follows 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?

There is no output schema, but the description compensates by stating what the list contains (every skill plus the grades each covers), which is exactly the return shape an agent needs. Combined with the no-parameter schema and clear annotations, nothing required for correct invocation is missing.

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 takes no parameters, so the schema carries no semantics to compensate for. Baseline 4 applies; the description's mention of `skill` and `grade` refers to input fields of the sibling tool and to returned values, not to this tool's own parameters.

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 (List) and resource (math skills Mathter can generate) plus the scope of what each entry includes (grades it covers). This is clearly distinct from the sibling generate_worksheet_pack, which produces worksheets rather than listing available skills.

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 tells the agent when to use it — to pick the `skill` and `grade` values needed by generate_worksheet_pack — and cautions against guessing a key. The alternative (guessing) and the sibling are both named, leaving nothing to inference.

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