Retrieve a company's detailed information by providing its unique QuickBooks CompanyInfo ID. Get the exact record you need from QuickBooks Online.
Get a specific CompanyInfo record by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| companyInfoId | Yes | The unique CompanyInfo ID |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description alone must disclose behavioral traits. It only states the retrieval action but does not mention read-only nature, permissions, error conditions, or any side effects.
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 a single sentence of 9 words, conveying the essential action efficiently with no redundant information.
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 simple get-by-ID tool with one parameter and no output schema, the description is functionally adequate but omits details like return value format or behavior when ID is not found.
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?
Schema coverage is 100% with one parameter described as 'The unique CompanyInfo ID'. The description adds no extra semantic value beyond what the schema already provides.
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 explicitly states the verb 'Get', the resource 'CompanyInfo record', and the method 'by its ID', which clearly defines what the tool does and distinguishes it from the sibling qbo_company_info_list tool.
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 the list variant (qbo_company_info_list). The description lacks any context for choosing between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.