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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), but the description adds real behavioral context beyond them: values are exact/unclipped, and page reads are capped with the cap signalled in the response. The silent-truncation risk of the sibling is a useful disclosure. It does not describe the return shape in detail, so not 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 key contrast (full copy vs get_page's clipping) in the first clause, and the cap disclosure earns its sentence. The middle em-dash clause is slightly verbose but not wasteful.

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?

With no output schema and only read-only annotations, the description carries the behavioral burden well: it covers the clipping distinction, the two request modes, and page-read capping. It stops short of describing the response structure or how capping is reported, but is complete enough to invoke correctly.

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 projectId undocumented in both schema and description. The description compensates by clarifying the tokens-vs-pageName modes and implying they are alternatives, which is more than the schema states. projectId remains unexplained, keeping it below 5.

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+resource (reads the FULL, unclipped copy in named slots) and explicitly distinguishes itself from uichemy_get_page, which clips at 80 characters. An agent can tell the two apart without opening either 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 the two selection modes directly ('Ask for the tokens you need, or name a page to read everything on it') and names the alternative with the condition that rules it out (get_page's 80-char clipping makes it useless for paragraph reads). Nothing is left to inference.

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