calculate_grade_average

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

No annotations exist, so the description carries full burden. It indicates the tool returns a weighted average and a missing-grade-needed forecast, implying pure computation. No side effects or permissions are mentioned, which is acceptable for a simple calculator but could be improved.

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 concise sentences with core functionality front-loaded. Could be more structured with bullet points, but all essential information is present without fluff.

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 simple tool with two parameters and an output schema, the description adequately covers inputs, output, and usage context. The reference to list_bundles adds helpful context for discovering related tools.

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 coverage is 100%, so baseline is 3. The description adds that coefficients are 'optional weights/weights', which slightly clarifies their role but is largely redundant with the schema descriptions.

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 computes simple or weighted grade average for school report cards, specifying inputs and outputs. It does not directly differentiate from siblings like 'calculate_average' but directs to list_bundles for related education calculators, which is moderately helpful.

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 provides a clear use case ('Use for school report cards') and hints at alternatives via 'list_bundles', but does not explicitly state when not to use this tool compared to specific siblings like 'calculate_grade_needed'.

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