deadlines

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

No annotations are provided, so the description carries full burden. It does not disclose whether the tool is read-only, requires authentication, or has side effects. As a calculation tool, it is likely safe, but the description does not confirm this.

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 that efficiently conveys the tool's purpose and output. While concise, it could be structured with bullet points for clarity, but it is still effective.

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 lists the main deadline types returned (annual return, accounts filing, tax return, etc.), which provides sufficient context. Parameters are well-documented in the schema. However, it lacks details on return format or error handling.

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 coverage is 100%, baseline 3. The description adds value by explaining how parameters (incorporationDate, accountingRefMonth, accountingRefDay) are used together to calculate deadlines, and mentions defaults for month and day.

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 tool's purpose: calculate all Gibraltar company compliance deadlines for a given year, listing specific deadline types. It distinguishes from siblings like 'annual_return' which likely covers only one deadline type.

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 description indicates usage based on incorporation date and accounting reference date for a target year, implying it's the comprehensive tool for Gibraltar deadlines. However, it does not explicitly exclude cases or compare to alternatives like 'annual_return' or 'poa_calculator'.

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