aws_paginate

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: returns nextToken and hasMore, explains the 5 MB cap, and describes the pagination loop. No contradiction with annotations. Slightly more context would elevate to 5, but already informative.

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?

Description is a single paragraph with front-loaded purpose. Every sentence adds value: purpose, relationship to sibling, return format, pagination loop, and usage guideline. No filler or redundancy.

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 no output schema and multiple parameters, the description covers the essential pagination pattern, return values, and reasoning for using this tool over aws_call. The agent can fully understand how to use the tool correctly.

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 description adds little beyond what the schema already provides. It mentions maxItems and startingToken in context, but this is more about usage than adding new semantic meaning. Baseline 3 is appropriate.

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 one page of a paginated AWS list/describe operation' and explicitly distinguishes from sibling aws_call by noting the added parameters (maxItems, startingToken) and the pagination loop. Specific operation examples (list-objects-v2, describe-instances) further clarify purpose.

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 advises using this tool instead of aws_call for operations that might exceed the 5 MB stdout cap and lists concrete examples. Describes the pagination pattern with nextToken and hasMore, telling the agent to call again until hasMore is false. Provides clear when-to-use and when-not-to-use guidance.

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