aws_docs_read

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral details: strips nav, cookie-banner, feedback before converting to markdown, and explains pagination behavior. No contradiction.

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?

Very concise: two sentences. First sentence covers purpose and URL constraint; second covers pagination and chrome stripping. No unnecessary words.

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?

No output schema, but description explains response includes hasMore and nextStartIndex, and that chrome is stripped. For a read tool with good annotations, this is complete—covers input, pagination, and output shape.

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 baseline is 3. The description adds context: for url, it reiterates the requirement and links to sibling tool; for startIndex and maxLength, it explains pagination flow and defaults. This adds value beyond 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?

Description clearly states 'Fetch an AWS documentation page and return it as markdown' and specifies that the URL must be from docs.aws.amazon.com, typically from aws_docs_search. This distinguishes it from sibling tools like aws_docs_search (which searches) and other tools.

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 states that the URL must be an https://docs.aws.amazon.com/...html page, typically from aws_docs_search. Explains pagination with startIndex and maxLength, and how to continue reading. No explicit when-not-to-use, but context is clear.

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