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

With no annotations, the description carries full transparency burden. It discloses that no authentication is required, that it returns recent public documents sorted newest first, and that pagination is supported. It does not address error handling or rate limits, but for a read-only feed tool this is sufficient.

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 extremely concise—two sentences plus parameter definitions—and front-loaded with the tool's purpose. Every piece of information is useful, with no fluff or repetition.

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 simple paginated read tool, the description covers the essential aspects: purpose, access requirements, sort order, and pagination semantics. The presence of an output schema means return values need not be described. It is complete for an agent to select and invoke 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?

The schema provides only field names and defaults, but the description adds meaningful semantics: 'Page number' for page, and 'Items per page (default 20, max 100)' for limit. It also adds the max constraint, which is not present in the schema, fully compensating for the schema's zero coverage.

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 'Browse the public recents feed of shared documents'—a specific verb ('Browse') and resource ('public recents feed') that clearly states what the tool does. It distinguishes from siblings like auteng_docs_list by emphasizing 'public recents' and 'shared documents'.

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 provides clear context: it's for browsing publicly shared documents, requires no authentication, and returns newest first. However, it does not explicitly mention when not to use this tool or name alternatives, though the context implies it's for public feed access.

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