finance_reconciliation_sweep

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

No annotations are provided, so the description must cover behavioral traits. It mentions auth/scoping but does not disclose whether the action is destructive, its side effects, rate limits, or output structure. This is insufficient for a mutation-like action.

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 short (4 sentences) and front-loaded with the verb 'Run'. No redundant information. Efficient but could be slightly more detailed.

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?

Despite having an output schema, the description lacks crucial context for a finance reconciliation sweep tool. No information about prerequisites, effects, or alternative tools. Agents would struggle to select this correctly.

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%, so the description adds meaning: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs'. This provides basic semantics but lacks detail on expected format or examples.

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 states it runs the 'finance_reconciliation_sweep' action and routes through a dispatcher, but it does not explain what the action does in business terms. The purpose is implied by the name but not clarified.

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 versus alternatives like finance_reconciliation_exceptions. The description only discusses routing context (JWT, tenant, company scope) but no when-to-use or when-not-to-use.

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