finance_pricing_decomposition

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

Annotations already flag destructiveHint=true, readOnly=false, openWorldHint=true, and idempotent=false. The description adds some useful context by noting the call routes through the domain-agent dispatcher under JWT, tenant, and company scope, but it never explains what side effects may occur or what the action can modify. It does not contradict the annotations.

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 compact and organized with an Args block, but the first sentence largely restates the tool name and adds little value. It is concise in length, yet not every sentence earns its place as a meaningful addition.

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 an open-world, destructive, domain-agent action with a huge sibling set, this description is far too thin. An agent cannot determine when to invoke it, how to structure inputs, what return value to expect, or how it differs from the dozens of related finance tools. The routing and scope note helps, but the overall context is incomplete.

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 must carry the parameter semantics. It only labels message as 'Free-text objective' and inputs as 'Optional JSON string of structured inputs', which is generic and does not convey what inputs finance_pricing_decomposition actually expects or what a valid structured payload 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 opens with 'Run the finance domain agent action finance_pricing_decomposition', which essentially restates the tool name and provides no actual explanation of what 'pricing decomposition' means or what outcome it delivers. It does not distinguish this from the many other finance_* domain-agent tools in the sibling 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?

There is no guidance about when to use this tool versus alternatives such as dispatch_domain_agent, finance_query_data, or other finance_* actions. The routing/scope sentence describes infrastructure, not selection criteria, leaving the agent without a basis for choosing this tool.

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