get_assignments

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It mentions 'active enrolled courses' and sorting by due date, but does not state side effects, permissions, rate limits, pagination, or error behavior. For a read-only list, more context would be expected, but the description adds little beyond the basic operation.

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 brief and front-loaded with the primary purpose. The args are listed clearly, though the account param is missing. It is concise without unnecessary fluff, but the structure could be improved to include all parameters.

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 description covers the core functionality and days_ahead, but misses the account parameter and offers no usage guidance or behavioral context. With two parameters and an output schema, the description is incomplete for confident invocation.

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 'days_ahead' with a default, but completely omits the 'account' parameter. This leaves a parameter undocumented, creating a gap for agents.

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 a specific verb 'List' with a clear resource 'upcoming assignments across all active enrolled courses' and adds the sorting criterion 'by due date'. This distinguishes it from sibling tools that target specific courses or different content types, making the purpose unambiguous.

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 given for when to use this tool versus alternatives. The description does not mention that course-specific assignments are handled by other tools, nor does it state any conditions, exclusions, or prerequisites. The agent is left to infer context.

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