quickbooks_list_entities

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

No annotations. Description only states it is a connector operation and routes through an endpoint. No disclosure of side effects, auth needs, or behavioral traits.

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?

Description is short but lacks necessary details. Front-loaded name but fails to provide useful information beyond repitition.

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 generic nature and sibling tools, the description should explain what entities are listed. It does not, leaving the tool incomplete despite an output schema.

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?

Single parameter 'arguments' with default '{}'. Description adds minimal meaning: 'JSON string of arguments for the connector operation.' With 0% schema coverage, this is insufficient.

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 it lists entities but does not specify which entities. Sibling tools like quickbooks_list_accounts indicate this is a generic list, causing ambiguity.

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 provided on when to use this tool versus more specific list tools. No exclusions or context given.

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