query

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

No annotations are provided, so the description carries the burden. It discloses that results are written to a file, default MAXRESULTS is 1000, most transaction fields are not filterable, and error responses include valid filterable fields. This is valuable behavioral context, though it could mention if the operation is read-only.

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 (three sentences plus an example) with no wasted words. It front-loads the action and resource, provides examples, and includes important constraints. Every sentence serves a purpose.

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 the tool's simplicity (one parameter, no output schema), the description covers all necessary aspects: what it does, how to use it, defaults, limitations, and error handling. It is complete for an agent to invoke correctly.

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 100%, so baseline is 3. The description adds the file-writing behavior and the hint about using 'query_account_transactions' for filtering, which adds value beyond the schema. However, the schema already covers entity types and MAXRESULTS, so the added value is moderate.

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 the verb 'Execute a QuickBooks query' and the resource 'using SQL-like syntax'. It lists supported entity types and provides examples. It also distinguishes from the sibling tool 'query_account_transactions' by directing account/department filtering there.

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?

Explicitly provides when to use (any entity type) and when not to (account/department filtering, directing to 'query_account_transactions'). Also mentions default MAXRESULTS and the note about non-filterable fields, guiding the agent on query construction.

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