get_assignment_details

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

Annotations already include 'readOnlyHint: true', so the read-only nature is clear. The description adds no further behavioral context (e.g., permissions, rate limits) beyond what is implied.

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 short and front-loaded with the main action. Including parameter descriptions is useful, but the Args block could be considered redundant given the schema. Overall, it's efficient.

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?

An output schema exists, so explaining return values is not required. However, the description does not elaborate on what 'detailed information' includes, leaving some ambiguity. It meets minimal completeness.

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 0%, so the description must compensate. It explains that 'course_identifier' is a course code or Canvas ID and 'assignment_id' is a Canvas assignment ID, adding value beyond the schema titles. However, more detail on formats or constraints would help.

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 'Get detailed information about a specific assignment', which is a specific verb-resource pair. It distinguishes from sibling tools like 'list_assignments' or 'get_assignment_analytics' by emphasizing a single assignment.

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 no guidance on when to use this tool versus alternatives such as 'list_assignments' or 'get_assignment_analytics'. It lacks context for choosing this tool.

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