calculate_gst_late_fee

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, covering safety and predictability. The description adds that output is a 'Late fee breakdown with CGST/SGST split,' but does not disclose other behavioral details such as penalty calculation cap behavior or edge cases. With annotation coverage, a 3 is appropriate.

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 compact and well-structured, with a purpose sentence, usage context, arguments, and return value. Every section is needed and squarely supports tool invocation.

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 tool has an output schema, annotations, and complete parameter schema, the description sufficiently covers behavior, inputs, and output type. It lacks explicit mention of edge cases such as nil liability fee adjustment, but overall it is complete enough for correct invocation.

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?

Although schema coverage is 100%, the description adds meaning by noting that annual_turnover is used 'for cap calculation' and clarifies has_nil_liability as 'True if nil return.' This goes beyond the plain schema descriptions and helps the agent understand how the parameters affect the calculation.

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 immediately states a specific action ('Calculate GST late filing penalty') with a specific resource. This distinguishes it from sibling tools like calculate_gst or calculate_income_tax, and the object of the calculation is clear.

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 explicitly says when to use it: 'Use when estimating late filing fees or planning compliance.' It does not mention alternatives or exclusion criteria, but the context is clear enough for an agent to select it appropriately among the siblings.

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