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

With no annotations, the description must carry the behavioral burden. It does disclose the content of the response (work, history, correction-derived rules, context), which usefully signals a read of accumulated knowledge, but it never states that the call is read-only, whether it can be large, or what happens when the client_id is unknown.

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?

A single front-loaded sentence with no redundancy; the colon-list structure communicates scope quickly. 'Context' is a slightly vague catch-all, but nothing is wasted.

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 no output schema, the description gives a reasonable inventory of returned content but no sense of shape, volume, or ordering. It is adequate to identify the tool but thin on what the agent will actually receive.

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% for the single client_id parameter, so the schema already explains its origin ('from list_clients'). The description adds no further meaning about the parameter, which is the expected baseline when the schema does the work.

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 the specific resource ('one client') and enumerates what it returns: work, history, rules learned from corrections, and context. The scope word 'one' implicitly distinguishes it from firm-wide siblings like what_the_firm_knows and list_clients, though no explicit retrieval verb ('get/return') is used.

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 sibling is named as an alternative. The only routing hint lives in the schema ('from list_clients'), not in the description, so an agent must infer that this is the per-client drill-down after listing.

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