get_upcoming_deadlines

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

No annotations are provided, so the description carries the full burden. It does disclose ordering (soonest-first) and that results include days remaining. However, it doesn't explicitly state that this is a read-only operation, what fields each deadline entry contains, or any data-freshness limitations. This leaves some behavioral ambiguity.

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 two sentences with no filler. The first sentence packs essential information (scope, sorting, days remaining) and the second clarifies the intended use case. It is well-structured and front-loaded.

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 list tool with no output schema, the description provides sufficient scope (specific AY/FY), ordering, and usage context. It would benefit from a brief note on response format or read-only nature, but given the simplicity and full schema coverage, it is largely complete.

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?

The input schema already provides complete descriptions for both parameters (limit and withinDays), so schema coverage is 100%. The description does not add any additional context about parameter usage, defaults, or interactions, so it doesn't go beyond the schema baseline.

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 lists upcoming Indian tax and compliance deadlines for a specific assessment year, sorted soonest-first with days remaining. This is a specific verb+resource+scope. However, it doesn't explicitly distinguish from the sibling tool get_compliance_calendar, which likely has overlapping functionality.

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?

Provides a clear use case: 'Use this to remind a taxpayer what is due next.' This gives context for when to invoke the tool. It doesn't explicitly mention when not to use it or alternatives, but the intended scenario is clear enough.

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