qbo_purchase_orders_get

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

No annotations are provided, so the description carries full burden. It states the action 'Get' which implies a read operation, but does not disclose any additional behavioral traits such as authentication requirements, rate limits, or return behavior when the ID is not found. For a simple getter, this is adequate but not exceptional.

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 efficient sentence with no wasted words.

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 tool's simplicity with one parameter and no output schema, the description adequately conveys the core function. It could mention that the record includes all fields, but this is generally expected.

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 schema already covers 100% of parameters with a description of purchaseOrderId. The description adds no further semantic meaning beyond restating 'by its ID', which is already implied by the parameter.

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 clearly states the verb 'Get' and the resource 'PurchaseOrder record', and specifies the method 'by its ID'. This distinguishes it from sibling tools like qbo_purchase_orders_list or qbo_purchase_orders_create.

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?

While no explicit when-to-use or when-not-to-use is given, the context of sibling tools (create, list, update, search) makes it clear that this tool is for retrieving a specific record by ID when the ID is known.

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