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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description goes well beyond that by disclosing the three generated artifacts, the default reminder offset of 2 days, the 29th-to-31st clamping rule, the weekend_rule shifting behavior, and the paycheck-assignment algorithm. It also explicitly disclaims any payment or bank-connection side effects, removing ambiguity about what the tool actually does.

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?

Three sentences, front-loaded with the when-to-use triggers before the parameter and behavior detail, and every clause carries information. The middle sentence is dense and long, packing data-entry guidance and the three outputs together, which slightly hurts scannability but wastes no words.

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 15-parameter, zero-required tool with an output schema and full annotation coverage, the description supplies everything an agent needs: trigger intents, data-shaping instructions, output formats, default behaviors, and explicit non-capabilities. Return values need not be re-explained because an output schema exists.

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%, so the baseline is 3; the description earns an extra point by adding precedence semantics the schema cannot express — bills should be structured with name/amount/due_day or due_date/frequency/autopay, paychecks with amount/frequency/first_date, pasted lists or screenshots should be converted into those fields, and bills_text is fallback only. It adds little about the remaining layout and date-order options, which the schema already handles.

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 opens with a concrete verb and resource (generate a bill payment calendar) and enumerates the concrete deliverables: a printable calendar PDF for 1 to 12 months, an ICS reminder file, and an Excel paycheck-to-bill plan. There are no siblings, but an agent could distinguish this from any other calendar or finance tool purely from the text.

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?

It names explicit trigger intents ('bill tracker printable', 'monthly bill calendar', 'bill reminders', 'which paycheck pays which bill') so the agent knows when to select it. It also states exclusion boundaries: it does not pay bills, connect to banks, or know bank holidays, and it designates bills_text as a fallback only.

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