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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, yet the description adds substantial context beyond them: chunked returns with a next_offset continuation protocol, automatic JavaScript rendering with a slower (~20 s) forced-render path, an "extraction" field indicating which path was used, and domain rejection. These are exactly the operational traits an agent needs and none are 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-loaded with purpose and scope, then usage routing, then pagination and rendering behavior, then exclusions. Dense and mostly earned, though it is a single long block and the rendering/extraction detail could be trimmed slightly for readability.

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 four-parameter read tool with an output schema, the description covers everything needed to call it correctly: where it applies, how to continue a long page, how rendering is chosen, and how the result is shaped. Return values are handled by the output schema, so no further detail is required.

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, but the description adds cross-parameter meaning the schema does not: it explains that continuation requires reusing the same url with offset set to next_offset, and that `render` defaults to automatic unless the plain fetch yields almost no text. It adds little about maxLength beyond what the schema says.

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 ("fetches one public page on siemens.com... returns its main content as clean markdown") and bounds it to three Siemens domains plus developer.siemens.com. This is clearly distinguishable from the search siblings, which the description names explicitly.

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 positive triggers (after siemens_search, siemens_productSearch or siemens_developer_search, or when the user supplies a Siemens URL) and explicit exclusions (not for searching - use siemens_search - and not for non-Siemens sites, which are rejected). 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.