quickbooks_get_entity

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

No annotations exist, so the description carries the full burden. It mentions routing and scoping (JWT, tenant, company) but does not disclose side effects, required permissions, idempotency, or whether the operation is read-only. This lacks sufficient behavioral detail.

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 but front-loads technical routing details that may not be actionable for tool selection. It could be more concise by omitting the routing line and focusing on functional behavior. Still, it avoids unnecessary verbosity.

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 lack of annotations and output schema, the description is severely incomplete. It does not explain what data the entity contains, what arguments are expected, or what the tool returns. For a potentially complex QuickBooks operation, this leaves the agent underinformed.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation.' This adds minimal clarification that the string is JSON, which is not explicit from the schema (type 'string'). However, with 0% schema description coverage and no further detail on expected structure, the description does not adequately compensate.

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 merely restates the tool name ('get_entity') without specifying what entity type is retrieved or the operation's scope. It does not differentiate from sibling tools like 'quickbooks_list_entities' or 'quickbooks_get_invoice', leaving the purpose vague.

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 such as 'quickbooks_list_entities' (to list all entities) or 'quickbooks_get_invoice' (to get a specific invoice). The description offers no context or exclusion criteria.

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