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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes the return shape (state, case counts, report offer), which is genuinely useful because no output schema exists, but it discloses nothing about lookup failure behavior or the nature of the 'report offer'.

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?

One short sentence-fragment with the key content front-loaded and no filler. It loses a point only because it is an under-punctuated fragment with no explicit predicate, which leaves the operation itself implicit.

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 one-parameter read tool with annotations and no output schema, listing the returned fields fills part of the gap. However, the description omits the prerequisite lookup step and what the 'attorney report offer' actually means, leaving material questions unanswered.

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?

With a single parameter at 100% schema description coverage, the schema already explains that 'id' is an Attorney ID sourced from search. The description adds no format, range, or provenance detail beyond that, so the baseline 3 applies.

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 is a noun phrase rather than a verb+resource statement, but it does name the resource (attorney) and the fields returned (state, total cases, resolved cases). It never states explicitly that it retrieves a single attorney, nor does it differentiate itself from the parallel siblings get_case/get_court/get_judge beyond the resource noun.

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?

There is no when-to-use or when-not-to-use guidance, and no mention that the 'id' must first be obtained from the search sibling. The only hint that a lookup precedes this tool lives in the schema's parameter note, not the description. An agent gets no routing logic from the text.

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