finance_investment_broker_account_snapshot

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

Annotations already carry the destructiveHint, readOnlyHint, and idempotentHint flags. The description adds useful context about routing through the domain-agent dispatcher and scoping under JWT, tenant, and company. However, it does not clarify the destructive nature or potential side effects beyond what the annotation already signals.

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 and structurally organized with an Args section, but the first sentence is redundant with the tool name. There is little wasted prose, yet the brevity stems from under-specification rather than purposeful conciseness.

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?

Even though an output schema exists, the description fails to convey the action's real-world function, how to phrase `message`, or what structured `inputs` may be required. The generic wrapper style leaves an agent without enough context to invoke this tool correctly or distinguish it from similar finance investment tools.

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 for the bare parameter names. It only states that `message` is a free-text objective and `inputs` is an optional JSON string, which largely mirrors the property names and types already present in the schema. It does not explain expected content, syntax, or constraints for either parameter.

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 restates the action name ('Run the finance domain agent action `investment_broker_account_snapshot`') without explaining what a broker account snapshot is or does. It provides routing context but no concrete verb+resource semantics, making it nearly tautological.

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 such as finance_investment_market_data_snapshot or finance_investment_broker_readiness_check. The description only mentions routing and JWT scope, not the conditions that should trigger this action.

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