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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false), and the description adds real mechanics beyond that: it computes the first nextDate and persists the rule. The confirmation note is somewhat redundant with the schema's own "Must be true to execute the mutation", and return behavior is unspecified.

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?

Two dense sentences that lead with the action and put the confirmation gate last where it belongs. The parenthetical enumeration is somewhat redundant with the schema but costs little.

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 10-parameter mutation with no output schema, the description covers the material behavior an agent needs: it persists a rule rather than posting a transaction now, it computes nextDate, and it requires explicit confirmation. What is returned after creation is left unstated.

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 parenthetical field list (amount, type, description, account, frequency, interval, startDate) largely restates the schema and omits the optional categoryId and idempotencyKey, adding no format or default semantics of its own.

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+resource ("Create a recurring-transaction schedule") and enumerates the fields that define the schedule, so an agent can tell it apart from add_transaction. It never explicitly names the one-off sibling as the alternative, which keeps it from a 5.

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?

"Requires confirmation: true to execute" is a genuine precondition for use, but there is no guidance on when to create a schedule versus using add_transaction or apply_template, and no mention of what happens when confirmation is false or omitted.

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