classroom_get_material

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

Annotations already declare readOnlyHint=true, and the description's 'Get' is consistent. It adds 'full details' and by-ID scoping, but does not disclose auth requirements, error behavior, or what 'full details' includes. Given the annotation coverage, this is acceptable but not rich.

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?

One sentence with no filler, front-loaded with the operation and object. It is appropriately compact for a simple getter tool.

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 definition is enough for a basic read call, but without an output schema or return description, 'full details' is vague. It also omits the relationship/requirement of courseId and how to discover the material ID, such as via classroom_list_materials. These gaps make it only minimally complete.

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?

Only 50% of parameters have schema descriptions: id is described as 'Material ID', but courseId has no description. The description says 'by ID' but does not clarify that both the material id and its parent courseId are required or how they relate. It adds little beyond the schema.

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 the verb 'Get', the resource 'course material', and the scope 'specific ... by ID', which clearly distinguishes it from list-oriented siblings like classroom_list_materials. The phrase 'full details' further separates it from summary-list operations.

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 this tool is for retrieving one known material by ID, but it does not explicitly say when to use alternatives such as classroom_list_materials when the ID is unknown. There is no when-not-to-use or alternative routing, so usage guidance remains implied rather than explicit.

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