patch_fee

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

With no annotations, the description carries all transparency burden. It indicates mutation via PATCH but does not explain side effects, idempotency, permissions, or error conditions, leaving significant gaps.

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 very short, but its brevity sacrifices clarity on parameter usage. It is concise but not well-structured for an agent, as it leaves ambiguity.

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 3 undocumented parameters, no annotation support, and similar sibling tools, the description is insufficient. It lacks parameter specifics, usage context, and does not leverage the output schema.

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 0%, yet the description only adds 'Use true or false' without mapping to parameters. It does not clarify fee_id requirement or meaning of billable/billed, offering minimal help.

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 toggles a fee's billable/billed state using PATCH, but does not differentiate from sibling update_fee which might also update these fields. The verb 'toggle' and mention of 'billable or billed' provide specificity.

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?

No guidance on when to use this tool instead of alternatives like update_fee or create_fee. No context about typical usage scenarios or prerequisites.

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