finance_stripe_ledger_reconciliation

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

The annotation marks destructiveHint as true, but the description only mentions 'surfaces' mismatches and variances, implying a read-only analysis. No side effects or write operations are disclosed, creating a contradiction between annotation and description.

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 concise and well-structured, consisting of a clear purpose statement, a list of observable outputs, and an Args section. It avoids unnecessary verbosity, though the parameter list is minimal.

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?

The description does not explain what the output summary looks like, how the 'message' parameter influences the execution, what 'month' is used for, or how the optional statement_url and materiality_threshold_usd affect the reconciliation. No output schema is provided, leaving the agent without critical context for expected results.

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?

The schema provides zero descriptions for any of the four parameters. The description only lists parameter names without explaining their meaning, format, or default behavior. For example, 'message' is described as 'Free-text objective' but no clarification is given on what kinds of objectives are expected.

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's purpose: 'Reconcile Stripe payment activity against your accounting ledger.' It uses a specific verb and resource, and distinguishes itself from sibling tools like stripe_dispatch or stripe_twin_list.

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?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., stripe_dispatch, stripe_raw_api_request). It does not mention use cases, prerequisites, or scenarios where another tool would be more appropriate.

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