get_customer_profile

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

With no annotations, the description discloses that the profile is 'fake internal', indicating a mock/test context. The read-only nature is implied by 'Retrieve'. Example IDs provide concrete behavioral context, though error handling is not discussed; the output schema likely covers return shape.

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 exactly two sentences with no filler. It front-loads the purpose and then provides useful examples, every word earning 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?

For a simple 1-parameter lookup tool with an output schema present, the description is nearly complete. It includes 'fake internal' context and example IDs, making it usable. However, it could explicitly state when not to use it (e.g., for real production data) or reference sibling alternatives for contrast.

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 0%, so the description compensates by providing example customer IDs (CUST-1001, CUST-2002), which clarifies the expected format beyond the schema's bare string type. This adds meaningful parameter guidance.

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 ('Retrieve') and resource ('customer profile'), clearly distinguishing it from siblings like get_product_info and get_api_endpoint_info. The 'fake internal' qualifier adds specificity about the data source.

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?

Context is clear: this tool retrieves customer profiles, and example IDs guide usage. It does not explicitly mention alternatives or exclusions, but the sibling tools are in different domains, making implicit differentiation sufficient.

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