quickbooks_payroll_company_info

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

Only mentions routing details (JWT, tenant, company scope). Lacks disclosure of behavioral traits such as read-only nature, data returned, or any side effects. No annotations to supplement.

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?

Short but not concise in conveying useful information. The phrase 'Quickbooks connector operation' is redundant and front-loads no actionable detail.

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?

Even with a single parameter and an output schema, the description omits core functionality entirely. An agent cannot determine what this tool does, when to use it, or what to expect as output.

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', adding no meaning beyond the input schema's type and default. Schema coverage is 0%, and the description does not 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 repeats the tool name as a 'Quickbooks connector operation' without stating what the operation does (e.g., retrieve payroll company info). It fails to provide a specific verb and resource, and does not help distinguish from sibling tools like quickbooks_company_info.

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 other QuickBooks tools. There is no mention of context, prerequisites, or alternatives.

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