finance_statement_ingest

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

Annotations already indicate this is not read-only and is destructive, and the description does not contradict them. The description adds some behavioral context by mentioning routing through the domain-agent dispatcher and scoping under JWT, tenant, and company identity, but it does not disclose what side effects occur during the ingest.

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, well-organized, and front-loaded with the action being run. The Args section is compact and readable, though the opening sentence is somewhat redundant with the tool name.

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?

For a tool with destructive annotations and a generic dispatch semantics, the description is not complete enough. An agent lacks the domain context needed to know what statement data to provide, what the action will do, or how it relates to the many sibling finance tools; the output schema exists but cannot compensate for missing operational meaning.

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 0%, so the description carries the documentation burden. It does explain message as 'Free-text objective' and inputs as 'Optional JSON string of structured inputs', which is more than the schema offers, but it never describes what structured inputs are expected or what a well-formed call looks like.

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 only says to 'Run the finance domain agent action `finance_statement_ingest`', which essentially restates the tool name without explaining what ingesting a finance statement actually accomplishes. The routing detail adds context but not domain semantics, so an agent cannot tell what outcome to expect or how this differs from related finance tools.

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?

There is no guidance on when to use this tool versus alternatives like dispatch_domain_agent or finance_query_data. The only usage-related information is that it routes through the dispatcher under JWT, tenant, and company scope, which is a mechanism detail, not a selection criterion.

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