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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool returns deadlines with enforcement dates, penalty information, and related obligations, and implies a read-only operation. It does not cover pagination or response format, but for a query tool the disclosure is reasonably transparent.

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, front-loaded with the core purpose and immediately followed by useful detail. Every sentence earns its place with no filler or redundancy.

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 output schema, the description explains return content reasonably well (deadlines with enforcement dates, penalties, related obligations). It does not mention default parameter behavior, but those are covered by the schema. Sibling differentiation is implicit but not explicit, slightly reducing completeness.

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 100%, so parameters are already well-documented. The description adds context about what the deadlines include (enforcement dates, penalties, related obligations) but does not add parameter-specific semantics beyond the schema. Baseline of 3 is appropriate.

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 'Returns upcoming and recent compliance deadlines' with specifics like enforcement dates, penalty information, and related obligations. This distinguishes it from sibling tools like check_obligations, which likely focuses on obligations rather than time-sensitive deadlines.

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?

The phrase 'Use this to understand time-sensitive compliance requirements' provides clear context for when the tool is appropriate. It does not explicitly mention alternatives or exclusions, but the temporal focus on deadlines versus other compliance aspects offers reasonable guidance.

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