classroom_get_assignment

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

The annotations already declare readOnlyHint and openWorldHint, so the read-only nature is covered. The description adds 'full details,' which hints at the response shape, but it does not disclose error behavior, permissions, or other operational traits. It is acceptable but minimal.

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, front-loaded sentence with no filler or repetition. It efficiently communicates the core purpose without unnecessary detail.

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 two-parameter read-only getter, the description is nearly sufficient. However, the lack of clarification about how the two IDs map to courseId and id, combined with no output schema, leaves some ambiguity for an agent deciding how to call it correctly.

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 only 50%, with only 'id' described in the schema. The description adds no meaning for 'courseId' and uses the generic phrase 'by ID,' which does not clarify that both courseId and id are required identifiers. It fails to compensate for the schema's missing courseId description.

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 specifies the action ('Get'), the resource ('assignment'), and the scope ('full details ... by ID'). This immediately distinguishes it from list-oriented siblings such as classroom_list_assignments without needing to inspect the schema.

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 phrase 'specific assignment by ID' implies this tool is for retrieving one known assignment rather than listing assignments, but it never explicitly names alternatives or states when not to use it. Guidance is present only implicitly.

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