finance_query_data

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

With no annotations, the description carries full burden. It mentions routing and scoping (JWT, tenant, company), which gives context. However, it does not explicitly state whether the tool is read-only or has side effects, nor does it disclose any behavioral traits like rate limits or error handling.

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 concise with three sentences and a list of arguments. It is well-structured, starting with purpose, then routing context, then parameters. No unnecessary information is present.

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?

Given that an output schema exists, the description is not required to explain return values. However, for a query tool, it could mention that the tool returns data or provide more context about the expected results. The description is minimally adequate.

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 coverage is 0%, so the description must explain parameters. It describes 'message' as a free-text objective and 'inputs' as an optional JSON string, adding meaning beyond the schema. However, it lacks examples or format details for the inputs 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 clearly states that the tool runs the 'finance domain agent action query_data', which indicates its purpose as a query tool within the finance domain. It distinguishes from sibling tools by specifying the finance domain, but could be more specific about the type of data queried.

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. The description does not mention any conditions for use, exclusions, or comparisons with other finance tools or domain query tools.

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