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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds the returned field list and repeats that the operation is read-only, but does not discuss PII sensitivity, permissions, or any limits. With annotations covering the safety behavior, this is adequate but modest.

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?

Three short sentences: field list, usage examples, and read-only note. The content is front-loaded and every sentence contributes useful selection or behavior information.

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 zero-parameter, read-only profile lookup with no output schema, the description provides enough content by listing the exact fields returned and giving usage examples. It does not need to explain inputs or return structure beyond the field enumeration, though it could mention sensitivity or freshness of the on-file data.

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 tool has zero parameters, so parameter semantics are not applicable and the baseline is high. The schema is empty and fully described by virtue of having no inputs, and the description correctly does not invent parameter behavior.

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 names a specific verb and resource — returning the customer's profile — and enumerates the exact fields returned (name, email, phone, billing address, company, account number). This clearly separates it from sibling catalog, DNS, and diagnostic tools, though it does not explicitly name an alternative.

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?

It gives concrete user-intent examples such as “what's my address on file?” and “what's my account number?”, which tells the agent when this tool is appropriate. It lacks explicit when-not conditions or named alternative tools, so it is clear but not fully prescriptive.

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