read_documentation

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

With no annotations provided, the description carries the burden of disclosing behavior; 'Read' conveys that the operation is non-destructive, which is the key safety trait for tool selection. However, it does not disclose error behavior for invalid paths, auth requirements, or content format, though an output schema exists to cover the return shape.

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?

A single sentence that leads with the verb, names the object, and qualifies the scope; there is zero wasted text. This is appropriately sized for a one-parameter read 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?

For a low-complexity read tool with a fully documented single parameter and an output schema, the essential information is present. The only gap is explicit routing guidance against the sibling search workflow, which is partially bridged by the schema hint that paths come from search results.

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 100%, so the single path parameter is already fully documented with an example and provenance ('returned in search results'). The description adds no parameter-level detail, but the baseline of 3 applies because the schema does the heavy lifting.

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 states a specific verb (read), a resource (an Azure documentation page), and scope ('full content' of a 'specific' page). This implicitly distinguishes it from the sibling search_documentation, which finds pages rather than returns their content, though the alternative is not named 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?

The description text gives no explicit when-to-use guidance, but the schema's path description ('This path is returned in search results') implies the intended workflow of searching first and then reading the chosen page. There are no exclusions or named alternatives, so the guidance is only implied.

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