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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent operation. The description adds useful behavioral context beyond that: only a licensed lawyer may accept, conflict-of-interest rules apply, and an API key is required. It does not describe what happens after acceptance or error behavior.

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 tight sentences and front-loads the action and scope. The API-key note is brief and useful, and there is no redundant or wasted text.

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 three-parameter mutation with no output schema and annotations covering the safety profile, the description supplies actor eligibility, request types, conflict constraints, and auth requirements. It omits idempotency/retry context, though the schema documents idempotencyKey.

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 description coverage is 100%, with explicit descriptions for side, caseId, and idempotencyKey. The description reiterates that the request is on the given side but adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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: accepting a pending request for counsel on a given side. It distinguishes the two relevant request types (open REPRESENT_PARTY opportunity vs one addressed to you), which helps separate it from siblings like decline_counsel_request and request_counsel.

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 clearly states the context for use: a pending request for counsel on the given side, either open or addressed to the caller. It also notes conflict-of-interest rules apply, but it does not explicitly name decline_counsel_request as the alternative or describe when not to accept.

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