quickbooks_list_classes

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

No annotations provided. The description only adds routing info (JWT, tenant, scope) but doesn't disclose whether the operation is read-only, idempotent, or any other behavioral traits beyond what is obvious from the name.

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 efficient in word count, but the routing detail appears before the usage context, and the parameter explanation is generic.

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 (not shown), the description omits return value details or side effects. For a list tool, more completeness is expected regarding the 'arguments' structure and what data is returned.

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?

The lone parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' but no structure or expected keys are provided. With 0% schema coverage, the description should compensate but does not.

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 the tool is a Quickbooks connector operation for 'list_classes', but does not explain what QuickBooks classes represent. It is a generic list operation among many similar siblings (e.g., list_departments, list_items) with no differentiation.

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 on when to use this tool versus alternatives. The description only mentions routing details, not usage context or exclusions.

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