patch_expense

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

No annotations provided; description only mentions toggling state with boolean strings, omitting details on side effects, idempotency, or required permissions.

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?

Single sentence, immediately conveys purpose and expected input format with no redundancy.

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?

Output schema exists, so return values are covered; description is sufficient for a simple toggle tool, though it could mention partial update nature.

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 0%; description adds meaning that values should be 'true' or 'false', but does not clarify expense_id or combination of parameters.

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?

Description clearly specifies verb 'Toggle' and resource 'expense entry's billable or billed state' and distinguishes from sibling tools like 'update_expense' and 'patch_fee'.

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?

Implies usage for toggling billable/billed state using 'true'/'false', but lacks explicit guidance on when not to use or alternatives like 'update_expense'.

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