get_hpe_document

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It provides valuable context: a normal web fetch returns an empty JavaScript shell, so this tool reads the underlying API; large documents are split into topics; calling without page returns the topic list; include_all_topics reads the whole document. This gives meaningful behavior beyond the schema, though it does not cover error behavior, rate limits, or response formatting.

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?

The description is front-loaded with the core purpose, then efficiently explains the technical workaround, parameter flexibility, and pagination workflow. Every sentence adds value and there is no redundant or filler content. The structure is easy to parse and directly supports correct invocation.

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?

Despite lacking an output schema and annotations, the description covers the essential usage workflow: how to pass a document, how to navigate topics, and how to retrieve everything at once. It explains why the tool exists and what makes it different from a normal fetch. The main gaps are the unaddressed max_chars parameter and lack of explicit return format details, but the core invocation path is well covered.

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 description coverage is 0%, so the description must compensate. It thoroughly explains document (bare ID or URL containing one), page (use topic's page value), and include_all_topics (read whole document at once). However, max_chars is never mentioned, leaving its meaning and interaction with pagination unclear. For three of four parameters, semantics are excellent; the omission of max_chars prevents a 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?

The description opens with a specific verb and resource: 'Read the full text of an HPE Support Center document.' It clearly distinguishes itself from siblings: list_hpe_document_topics only lists topics, search_hpe_kb searches, and this tool retrieves full document text. The scope is explicit and leaves no ambiguity about the tool's function.

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?

The description states 'Use this for any support.hpe.com document - release notes, advisories, customer notices, product documentation,' which clearly establishes when to use the tool. It also explains the topic-picking workflow with page and include_all_topics. However, it does not explicitly name alternative sibling tools or state when not to use them, so it stops short of a full 5.

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