kilter_get_grade_pyramid

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

Annotations already cover read-only and non-destructive behavior. The description adds useful behavioral details: the pyramid is ordered hardest first and includes flash rates, and the angle parameter filters by wall angle. It does not contradict annotations and provides context beyond them.

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 sentences, no waste. The first sentence states the core function; the second gives usage guidance and the filter. The primary purpose is front-loaded and every clause adds value.

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?

The tool has an output schema, so return format is covered elsewhere. With one optional parameter explained, clear usage guidance, and annotations for safety, nothing an agent needs to call it correctly is missing. Complexity is low, and the description is fully sufficient.

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 has 0% description coverage for the 'angle' parameter, so the description must explain it. It does: 'Optional wall-angle filter.' This gives the parameter meaning (a filter on wall angle) and clarifies it is optional. Though it lacks units or range, it sufficiently compensates for the schema gap.

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 returns a send pyramid with sends per grade, hardest first, and flash rates. It uses a specific verb and resource, and the usage triggers ('grade pyramid', 'distribution of grades', 'flash rate per grade') distinguish it from siblings like kilter_get_hardest_sends and kilter_get_progression.

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 explicitly lists when to use the tool ('when the user asks about their grade pyramid, distribution of grades, flash rate per grade, or how solid they are at a level') and mentions the optional angle filter. However, it does not explicitly name alternatives or state when not to use it, so it lacks exclusions.

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