commerce_cash_position

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

Annotations already provide readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the description is not obligated to restate them. It adds useful scoping context about the JWT, tenant, and company scope, but says nothing about side effects or consequences of running this 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, front-loaded with the primary action, and uses a clean Args block. The routing sentence is slightly platform-specific but earns its place by clarifying scope; no wasted words.

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 that may be selected among dozens of commerce wrappers, the description is incomplete: it lacks the business meaning of cash_position and any signal about when to invoke it. The output schema may define the return shape, but it cannot substitute for missing selection context.

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?

With 0% schema description coverage, the description must compensate, and it does provide a small Args section: message is a free-text objective and inputs is an optional JSON string of structured inputs. This is minimally meaningful but does not explain what should go inside the JSON or how the message is used by the underlying action.

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 a specific action ('Run the commerce domain agent action `cash_position`'), but it never says what cash_position actually does or returns. It is closer to a restatement of the tool name with routing details, and it does not distinguish itself from the many sibling commerce_* domain-agent wrappers.

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 is given for when to use this tool versus any alternative. It does not mention the intended use case, exclusions, or sibling tools such as commerce_inventory_check or commerce_revenue_by_product. An agent must infer selection purely from the name.

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