get_assignment_details

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

No annotations are provided, so the description must carry the full behavioral burden. It states this is a 'get' operation, implying read-only, but does not state so explicitly. It does not mention any side effects, permissions required, rate limits, or error conditions. The lack of any behavioral context beyond the action verb leaves agents uncertain.

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 with no redundant words. It is front-loaded with the action ('Get full details') and the object ('one assignment'). Perfectly concise and to the point.

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 existence of many sibling tools and the minimal description, the definition is incomplete for an agent to use it correctly. While the output schema exists (which explains return value structure), the description does not clarify the input parameters, usage context, or how it differs from similar tools. The tool is simple, but the description leaves too much unstated.

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 for the parameters. Both parameters (course_identifier and assignment_id) are named but not explained. The description does not clarify their formats, required types, or how they relate (e.g., whether assignment_id is scoped by course_identifier). No additional meaning is provided beyond the raw parameter names.

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 it retrieves full details for a single assignment, including the description. It distinguishes itself from list_assignments (which lists all) and get_assignment_analytics (which focuses on analytics). However, it does not enumerate what 'full details' encompasses beyond description, leaving some ambiguity about the exact scope.

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 is provided on when to use this tool versus its siblings. There is no mention of alternatives like list_assignments for viewing summaries or get_assignment_analytics for metrics. The intended use case (fetching a specific assignment's details) is implied by the name and description, but not explicit.

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