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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: the authentication flow, the epistemic caveat that it lists citations but not whether a source was followed or distinguished, and the warning that results are a slice controlled by `provisions_total`. It does not spell out the full response envelope (data_as_of, notes, truncated handling beyond max_chars), which keeps it short of a 5.

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?

Front-loads the mandatory sign-in step, then purpose, directionality, caveat and result-slice warning in a logical order; every sentence carries operational weight. Minor redundancy: the `provisions_total` caution and the slice caveat are repeated in both the description and the `limit`/`document_id` schema 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 six-parameter tool with no output schema, the description covers the auth prerequisite, what an edge contains (pinpoint, court, date, citing sentence), the partiality signal (`provisions_total`), the compact/full quote tradeoff, and the interpretive limit. An agent has enough to call it correctly and to read the result without guessing.

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%, so the baseline is 3; the description adds selection guidance the schema only implies — pass the search hit `id`, an article id with `#` scopes to that article versus a whole document, and there is no separate `pinpoint` parameter — plus a concrete example argument object. It still mostly restates what the schema already documents for `document_id` and `limit`.

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 and resource ('What one document or article relies on... the acts and earlier rulings it cites, each with its pinpoint, court and date and the citing sentence'), and explicitly names the sibling it is not: 'for the reverse direction ... use cited_by'. An agent can distinguish it from cited_by and read_paragraphs without opening a schema.

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?

Gives explicit when-to-use ('to follow a ruling's reasoning back to its sources'), the named alternative for the opposite direction (cited_by), and the follow-up needed to judge agreement (read_paragraphs). It also states the sign-in prerequisite and sequence (connect, then connect_verify) up front.

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