finance_list_cross_domain_scenarios

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

With no annotations, the description must fully disclose behavior. It mentions routing and scopes (JWT, tenant, company), but omits whether the operation is read-only, any rate limits, pagination, or error conditions. This is insufficient for a list operation.

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 very concise, with two sentences and bullet points for arguments. It is front-loaded and contains no fluff, though the first 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?

Despite having an output schema, the description does not indicate what the tool returns (e.g., a list of scenarios). It lacks context about the output structure or behavior when there are no results, making it incomplete for a list operation in a complex domain.

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 explain parameters. It describes 'message' as 'free-text objective' and 'inputs' as 'optional JSON string of structured inputs', which adds meaning beyond the bare schema names. However, it does not explain how inputs affect the listing or provide examples.

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 'Run the finance domain agent action list_cross_domain_scenarios', which essentially restates the tool name without clarifying what the tool actually does. It fails to explicitly say that it lists scenarios, and does not differentiate from sibling tools like finance_run_cross_domain_scenario.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or that this tool lists scenarios while finance_run_cross_domain_scenario executes them.

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