get-rubric-statistics

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

The annotation readOnlyHint=true covers the safety profile, and the description is consistent with it. However, the description adds no additional behavioral context, such as return format, pagination, error conditions, or what 'statistics' includes. It merely restates the purpose without enriching the behavioral understanding.

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 a single sentence, front-loaded with the verb 'Get', and contains no unnecessary words. It is highly concise and well-structured.

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 is a simple read-only getter with well-documented schema and annotations, but without an output schema, the description does not explain what statistics are returned or how includePointDistribution affects the output. It is adequate but leaves some gaps in expected information.

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 description coverage is 100%, so the schema fully documents all three parameters. The description adds no extra parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 retrieves statistics for rubric assessments on an assignment. The verb 'get' and resource 'statistics for rubric assessments' are specific, and the scope ('on an assignment') is clear. It distinguishes from siblings like list-rubric-assessments by focusing on aggregate statistics rather than individual assessments.

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 when statistics are needed, but provides no explicit guidance on when to use this tool versus alternatives such as list-rubric-assessments or list-assignments. There is no mention of exclusions, alternatives, or prerequisite conditions.

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