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

Adds substantial behavior beyond annotations: per-credential allowance bounded by the agent's 30-day limit or pilot end, idempotency in quota terms, premium-content exclusion, pilot global-budget dependency, and no auto-renewal. These are real operational constraints not present in the annotations.

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 return/retry purpose, but the premium header sentence ('keep evaluation.access_code...') and pilot-budget caveat make it feel like multiple concepts are packed into one block without clear grouping. Several sentences earn their place; the premium instruction is the least clearly scoped to this tool.

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, the description supplies the key return shape ('text per page with the hash of the source') and covers quota/pilot constraints. It leaves retry_after_s origin and polling/error behavior implicit, but the core call context is present.

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%, and both id and agent_pass are fully described there. The description adds quota meaning to agent_pass ('per credential') and references premium headers, but it does not add syntax or selection detail beyond the schema.

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 that it returns the text per page with the source hash after the basic reading's retry_after_s. The 'follows...after retry_after_s' phrasing identifies it as the result/continuation of evaluation_basic, but it never names evaluation_basic or explains how the retry value is obtained, so sibling differentiation is implicit.

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?

Explicitly says to call it after retry_after_s and notes that repeating the same document consumes no additional unit. It also states basic does not open premium content, giving a when-not boundary, but it stops short of naming evaluation_premium or evaluation_quota as alternatives.

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