Continue Accounting Workflow

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

Description claims 'resolve review item' and 'prepare approval action' implying mutations, but annotations declare readOnlyHint=true. This is a direct contradiction, making the description misleading.

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 covering three actions. Concise but lacks depth on each action's specifics. Could be improved with more detail without becoming verbose.

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?

No output schema and missing explanation of workflow lifecycle, return values, or how to obtain workflow_state_json. Insufficient for an agent to fully understand the tool's context.

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%. Description adds value by explaining that 'next' reads workflow_state_json and other actions read review_item_json, aiding parameter selection beyond schema.

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 states it continues an accounting workflow, resolves reviews, or prepares actions. It lists three actions but could be more precise about the resource and scope.

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 vs siblings like 'recommend_workflow' or 'suggest_booking'. Description lacks context for selection.

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