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

With no annotations provided, the description carries the full burden of behavioral disclosure. It declares 'Read-only' and 'over synthetic data', which is useful, but it does not explain error handling, limits, what 'bounded workflow guidance' means, or how the output varies with input combinations. The behavioral description is minimal and undetailed.

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, concise sentence that front-loads the core purpose ('Read-only billing or service-incident lookup') and then adds the supplementary workflow guidance. It is well-structured and avoids unnecessary verbosity, though it could be more detailed without losing conciseness.

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 complexity of the schema (11 optional parameters, only 1 required) and the absence of annotations and parameter descriptions, the description is heavily underspecified. It does not explain how to select parameters based on the category, what 'bounded workflow guidance' entails, or what the output schema contains. An agent would face significant ambiguity in correctly forming a request.

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 description coverage is 0%, so the description must compensate for missing parameter documentation. It does not explain the meaning or usage of any of the 11 parameters, nor does it clarify which parameters are relevant for 'billing' vs 'service-incident' or how the 'category' field drives the lookup. The parameter names are self-explanatory, but the description adds no additional semantics.

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 clear verb ('lookup') and resource ('billing or service-incident'), and also mentions additional workflow guidance. It implicitly distinguishes from the sibling `lookup_customer_account` by domain, though without naming it explicitly. The purpose is specific and understandable.

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 does not provide any explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or conditions. The phrase 'for account/other requests' is vague and does not clarify selection criteria. No alternatives are referenced.

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

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

With no annotations, the description must carry the full burden. It discloses the read-only nature and that it returns misses or mismatches, which is useful. However, it does not explain how multiple parameters combine, whether authentication is needed, or any other behavioral details beyond these basics.

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 two concise sentences with the key fact 'Read-only exact lookup' front-loaded. Every clause earns its place, and there is no redundancy or filler.

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 tool with 4 optional parameters, zero required, and no parameter documentation, the description is inadequate. It does not explain how to construct a valid lookup, what happens if multiple params are provided, or what escalation evidence looks like. The output schema exists but the description offers no context on call semantics.

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 description coverage is 0%, so the description must compensate for the lack of parameter documentation. It does not mention email, ticket_id, account_id, or account_number at all, nor does it explain whether at least one is required, how they interplay, or which is preferred. The agent has no guidance on parameter usage.

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 clear verb and resource ('Read-only exact lookup in the synthetic customer account system'), which distinguishes it from the sibling tool by resource. However, it doesn't explicitly name the sibling, so differentiation is implied rather than explicit.

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 gives no explicit guidance on when to use this tool versus the sibling lookup_billing_or_incident. The only usage-related hint is 'Use returned misses or mismatches as escalation evidence,' which concerns result handling, not tool selection. It lacks any exclusions or alternatives.

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