Get a PowerOffice customer

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context by noting the compact default field set and the effect of supplying Fields. It does not discuss error behavior or auth, but for a simple read with strong annotations this is sufficient.

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?

Two tightly written sentences with no filler. The core operation and endpoint are front-loaded, and the field-set behavior is stated in a single follow-up sentence. Every word earns its place.

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?

The tool is simple: one required ID parameter and one optional fields parameter. The description addresses both, names the endpoint, and the output schema covers return values. Nothing critical is missing for an agent to call this tool correctly.

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 only 50% because id lacks a description. The description compensates by explaining that id is the PowerOffice numeric ID and by clarifying that fields controls whether the compact or full field set is returned. This adds meaningful semantics beyond the raw schema.

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 states a specific verb ('Read'), a specific resource ('one customer by PowerOffice numeric ID'), and the exact endpoint ('GET /Customers/{id}'). This clearly distinguishes the tool from siblings like poweroffice_search_customers, poweroffice_create_customer, and poweroffice_update_customer.

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 description clearly implies usage when you already have a PowerOffice numeric ID and need a single customer. It does not explicitly mention alternatives or when not to use the tool, but the context is clear enough for an agent to select it over search or mutation tools.

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