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

With no annotations, the description carries the full burden. It discloses the auth requirement and implies a read-only list operation, but it does not describe side effects, pagination behavior, sorting, or how the returned documents are structured beyond what the output schema would already communicate.

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 well-structured: a one-sentence purpose, a brief auth note, and a clear parameter list. Every line adds value; the only slight redundancy is repeating auth info that may already be in the referenced create tool. Overall, it is efficient and easy to scan.

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 straightforward list operation with an output schema present, the description covers all parameters and the auth requirement. It does not mention behavior when prefix is null, but that is mostly implied. It is sufficiently complete for the tool's complexity.

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 Args block explains every parameter with meaningful context, including format constraints ('checksummed wallet address', 'Unix timestamp in seconds', 'Random hex string (32 chars, single-use)') and the optionality of prefix. This fully compensates for the schema's 0% description 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 'List documents in the agent's workspace,' a specific verb and resource that clearly conveys the core purpose. It distinguishes from create/delete/update siblings, though it does not explicitly contrast with the 'recent' tool that may also list 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 states the EIP-191 wallet signature auth prerequisite and refers to auteng_docs_create for auth details, but it gives no guidance on when to prefer this over alternatives like auteng_docs_recent, nor when not to use it. Usage context is implied but not explicit.

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