get_customer_profile

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 explains what data the profile includes but does not mention whether the operation is read-only, how missing customers are handled, or any potential side effects. This is a reasonable but not exhaustive disclosure for a simple profile lookup.

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 sentences, front-loaded with the core purpose, and uses a clear list of included data. No redundant words; every sentence adds value.

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 simple one-parameter schema and absent output schema/annotations, the description compensates by enumerating the profile fields and providing use cases. It lacks details on error conditions or data limitations, but is otherwise sufficient for a low-complexity tool.

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 the schema describing 'customer_name' as the exact name in ERPNext. The tool description adds no additional parameter semantics beyond what the schema already states, so it does not elevate beyond the baseline of 3.

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 tool's function: viewing a customer's complete profile with specific included data (purchase history, favorite products, last visit, total spent). This distinctly separates it from sibling tools like get_top_customers or get_inactive_customers, which focus on customer aggregates rather than individual profile details.

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 provides explicit usage context: 'Utiliser pour personnaliser le service ou préparer une relance.' This tells the agent when to use the tool. However, it does not explicitly mention alternatives or when not to use it, though the sibling tool list makes those distinctions implicit.

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