Upcoming Tax Deadlines

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

With no annotations, the description carries the full transparency burden. It tells what it does (shows deadlines) and mentions 'filing and payment' types, but does not disclose edge-case behavior such as empty results, whether the window is relative to today, or any side effects. It is adequate but not rich.

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 concise sentences that front-load the primary purpose and then add the window detail. There is no fluff or redundancy, making it efficient and easy to parse.

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 tool with no output schema and no annotations, the description leaves ambiguity about what 'upcoming' means (from today vs. from fiscal year-end) and does not describe the return format. It is adequate for a simple tool but has clear gaps that could force an agent to guess.

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 schema already provides 100% coverage with clear descriptions for both parameters (fiscal_year_end and days_ahead). The description's references to 'fiscal year-end' and 'specified window' add no new information beyond what the schema documents, so it stays at the baseline of 3.

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 verb 'Show' and the resource 'upcoming tax filing and payment deadlines', with the basis 'fiscal year-end' and 'specified window'. It is specific and self-contained, though it does not explicitly distinguish itself from a sibling like 'filing_calendar'.

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?

It provides clear context: use when you want upcoming tax deadlines within a specified window based on fiscal year-end. However, it does not mention exclusions or alternative tools, so it stops short of explicit when/when-not guidance.

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