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

Annotations only declare readOnlyHint=true; the description adds real behavioral context: the response is organized by pages and sections, includes references and image descriptions, and leads with a change list. It also discloses that long responses are chunked and resumed via nextCursor, which the annotations do not cover.

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?

Three compact sentences, front-loaded with what is returned, then response ordering, then pagination. No filler or restated metadata; every sentence carries information an agent needs.

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 carries the burden of describing the return shape and does so well (pages, sections, references, image descriptions, change list first). Minor gaps remain, such as how large a 'part' is or whether the cursor expires, but the essentials for correct invocation are 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 there is only one optional parameter, so the baseline is 3. The description goes further by explaining the cursor contract: pass the nextCursor from the previous response into cursor, which tells the agent how to drive the loop rather than just what the field is.

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 resource and scope: the complete website content, structured by pages and sections. 'Komplette' implicitly distinguishes it from the sibling section/summary tools, but no alternative is named explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by the word 'komplette' (use this when you need everything, not a section or summary), and the pagination continuation rule is stated clearly. However, there is no explicit when-to-use / when-not-to-use guidance relative to content_section, content_summary or answer_question.

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