qbo_read_company

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Read' clearly signals a non-mutating operation, and 'connected' hints at an authentication prerequisite, but the description does not disclose what the profile contains, what happens if no connection exists, or any other runtime behavior.

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?

A single, front-loaded sentence states the verb, object, and connection context with zero filler. Every word contributes meaning, making this appropriately concise for such a simple tool.

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?

For a zero-parameter read operation with no output schema and no annotations, the description provides enough information for an agent to select and invoke the tool correctly. Minor gaps are the lack of explicit return-value detail and any statement about ordering relative to qbo_oauth, but neither is necessary for basic invocation.

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 input schema has zero parameters, so schema-description coverage is vacuously 100%. With no parameters to document, the description does not need to add parameter-level detail, and the 0-parameter baseline of 4 applies.

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 uses a specific verb ('Read') and a specific resource ('connected QuickBooks Online company profile'), making the tool's purpose immediately obvious. The resource is distinct from the sibling tools, which target OAuth, employees, salary, and payroll, so there is no ambiguity about what this tool retrieves.

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?

The phrase 'connected' implies this tool should be used after OAuth has been established, but the description does not explicitly state when to use it versus alternatives or mention any exclusions. For a simple read-only tool, the usage context is reasonably implied, but no explicit routing guidance is provided.

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