get_deadlinesRetrieve upcoming tax and filing deadlines to stay compliant and avoid missed submissions. Filter by completed status when needed.
Get upcoming tax and filing deadlines
| Name | Required | Description | Default |
|---|---|---|---|
| include_completed | No | Include completed deadlines |
Changes observed during successful MCP inspections.
v0.2.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds the 'upcoming' scope, useful behavioral context, but it does not disclose output fields, date-range behavior, or formatting. No contradiction with annotations.
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 filler. It front-loads the action and resource, and every word earns its place. It is appropriately sized for a simple read-only tool.
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 low complexity and helpful annotations, this is minimally sufficient, but it lacks an output schema or any description of what the returned deadlines look like. It also does not connect to create_deadline or other related tools, leaving some contextual gaps.
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 for the single parameter include_completed. The description adds only the 'upcoming' context, which hints at default exclusion of completed deadlines, but contributes no additional parameter semantics beyond the schema.
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 uses a specific verb ('Get') and clearly identifies the resource as 'upcoming tax and filing deadlines'. It is clear and unambiguous, but it does not explicitly distinguish itself from siblings like create_deadline or get_tax_facts, so it falls short of a 5.
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 usage guidance is provided. The description does not say when to prefer this over related deadline or tax tools, nor does it identify alternatives or exclusions. An agent must infer when and how to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.