managebac_get_gpa

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

The description only mentions the error behavior but does not disclose whether the tool is read-only, what the return format is, or any other behavioral traits such as authentication needs or rate limits. With no annotations, the description fails to provide sufficient transparency.

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?

Single sentence that is front-loaded with the primary action. No wasted words; every part contributes to the purpose.

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 absence of an output schema and annotations, the description should compensate by explaining return values, default behavior, and how this tool fits with siblings. It does not, leaving the agent poorly informed.

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 the schema already documents both parameters. The description adds no additional semantic meaning beyond what is in the schema, earning the baseline score of 3.

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 states 'Read explicit GPA from ManageBac,' which clearly identifies the action and resource. However, it does not distinguish between this and sibling tools like managebac_get_class_gpa, leaving ambiguity about what 'explicit' means relative to computed GPAs.

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?

No guidance on when to use this tool versus alternatives like managebac_get_class_gpa or managebac_get_grades. The error condition ('returns an error when no explicit GPA is visible') is noted but does not provide actionable decision criteria.

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