managebac_get_all_deadlines

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

No annotations are provided. The description is minimal and does not disclose whether the tool is read-only, any authentication requirements, rate limits, or effects on data. It only implies a read operation through the verb 'Get'.

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 concise sentence with no unnecessary words. It front-loads the core purpose. However, it could be slightly more informative without sacrificing brevity.

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 no annotations, no output schema, and three parameters, the description lacks completeness. It does not explain return format, sorting, pagination, or the meaning of 'upcoming' relative to parameters like 'daysAhead'.

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 coverage is 100% with descriptions for all three parameters. The tool description adds no additional meaning beyond the schema. Baseline of 3 is appropriate as the schema already explains parameter purpose.

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 the action ('get all upcoming... deadlines') and resource ('ManageBac DDL/deadlines across classes'). It distinguishes from sibling 'managebac_get_class_deadlines' by specifying 'across classes', indicating a broader 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 on when to use this tool versus alternatives like 'managebac_get_class_deadlines'. The description does not mention prerequisites or context. It implies use for all-class deadlines but lacks explicit exclusions.

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