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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the shape of returned data and warning that default/saved addresses may not reflect an existing order's actual shipping address – a real semantic caveat an agent would otherwise get wrong.

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 sentences, front-loaded with the purpose and field inventory, then the caveat. The field list is long but each item is informative; the caveat earns its place. Title duplicates the description text, which is slightly redundant but not harmful.

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?

There is no output schema, so the description must convey what comes back – and it does, at field-group granularity, plus an interpretive warning. Gaps remain around the 'case' identifier and any auth/permission requirements, but for a read-only fetch with annotations it is largely complete.

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 67%, with company and environment documented but the required 'case' UUID parameter undocumented in both schema and description. The description implies scope to a single case customer but adds no format, sourcing, or cross-parameter meaning. Baseline 3 for a moderately documented 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?

States a specific verb (Read) and resource (the case customer's profile) and enumerates the returned fields: name, DOB, contact details, addresses, per-order addresses. That inventory distinguishes it from the broader summer_cases_get sibling, though no sibling is named explicitly.

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 sentence 'A saved address does not prove where an existing order ships' is genuine guidance about how to use the result (prefer per-order addresses over defaults). However, it never states when to call this versus summer_cases_get or summer_cases_assignment_read, and no prerequisites are given.

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