Calculate mechanics lien deadlines

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

With no annotations, the description discloses what the tool returns (dates, days remaining, warnings) and boundaries (all states, not legal advice). It doesn't fully detail output format or edge-case behavior, but the main behavioral contract is clear.

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?

Four short sentences, each earning its place: function, requirements, return value, and coverage/disclaimer. Front-loaded with the core calculation before details.

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 covers purpose, required inputs, outputs, and scope, while the schema covers optional parameters. Minor gaps remain around exact output formatting and error handling, but these are not critical given schema coverage.

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 the schema already documents all 5 parameters. The description adds only that invoice_date can be a delivery date, which the schema already states, so it doesn't materially increase semantic clarity.

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?

States a specific verb and resource: calculates preliminary notice and lien filing deadlines for US construction invoices. It also distinguishes itself from sibling guide/list tools by describing a computation rather than a reference lookup.

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 clear invocation criteria: needs invoice/delivery date and state, and covers all 50 states plus DC. It doesn't explicitly name sibling alternatives or state when not to use it, so it stops short of a 5.

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