finance_finops_attribution

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful auth/routing context by stating the action runs "under your JWT, tenant, and company scope," which helps an agent understand execution context. However, it does not disclose what side effects may occur or why the action is destructive, so it adds only modest value beyond 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, with a clear Args section and no filler. The first sentence is somewhat redundant with the tool name, but the routing context and parameter lines earn their place. It is front-loaded and easy to scan.

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?

Although an output schema exists and annotations cover some behavioral traits, the description is not complete enough for correct tool selection. It never states what finance_finops_attribution does, what problem it solves, or when an agent should invoke it. For a domain-agent action with only a generic message/inputs interface, this missing purpose and selection context is a significant gap.

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 compensate, and it does provide basic semantics: "message: Free-text objective" and "inputs: Optional JSON string of structured inputs." This adds meaning beyond the bare schema names and defaults, but it is still vague about what structured inputs are expected or how message and inputs relate. The parameter descriptions are minimally adequate, not detailed enough for confident non-trivial use.

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 says only "Run the finance domain agent action `finance_finops_attribution`," which essentially restates the tool name and gives no actual outcome, resource, or effect. It mentions routing "through the platform's domain-agent dispatcher," but that explains mechanism, not what the action does. An agent cannot infer what "attribution" is supposed to accomplish from this text.

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 the many finance_* siblings or generic dispatchers like dispatch_domain_agent. The routing and scope sentence provides context but no selection criteria, exclusions, or alternatives. Relying on the tool name alone is required.

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