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

Annotations already establish the safe read-only, idempotent, non-destructive profile, and the description adds substantial extra context: the .ics format, an all-day event roughly 30 days before the deal ends, alerts at 9am the day before and on the day, embedded script/offers/confirm-in-writing content, and that nothing is stored. This is meaningful disclosure beyond the annotations, though it doesn't mention rate limits or error behavior.

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 front-loaded with the core purpose, then layers the return details. Every sentence contributes (format, timing, contents, storage, relationship to the script endpoint). It is slightly dense but not padded, and no sentence is wasted.

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?

With no output schema, the description correctly compensates by describing the returned .ics contents, timing, and alerts, and by clarifying the privacy stance ('Nothing is stored'). Combined with full schema coverage of inputs, an agent has enough to invoke it correctly; only edge details like error handling are absent.

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 all four parameters (bill, country, provider, deal_ends) are already documented in the schema, and the description largely defers to it ('as for getBillScript'). It clarifies that deal_ends is the date the current price/policy ends, adding mild value, but the baseline of 3 is appropriate when the schema does the heavy lifting.

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 names a specific action and output: it produces a calendar reminder (.ics) to call before a deal ends, stating the timing and contents of the event. This clearly distinguishes it from siblings like lowermybill_get_bill_script (which returns a script, not a calendar file). An agent can tell what this tool produces without opening the schema.

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?

Usage is implied rather than stated. It notes '/v1/script gives this link as add_to_calendar when deal_ends is given,' hinting this is the downstream follow-up to getting a script, but it never explicitly says when to prefer this over calling get_bill_script directly or gives any prerequisite/exclusion. A capable agent can infer the context, but it is left to inference.

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