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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly requires EIP-191 wallet signature auth, a critical non-obvious behavior, and lists all auth-related parameters. It does not explicitly state read-only, but 'list' implies a non-destructive operation. The prefix filter behavior is also disclosed.

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 compact and front-loaded with the primary purpose, followed by the auth requirement and a straightforward Args list. No redundant or filler text. Every sentence adds value, and the structure is scannable.

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?

Given the presence of an output schema, the description need not explain return values. It covers the tool's core purpose, auth requirements, and all parameters. It does not mention limitations like pagination or ordering, but for a straightforward list tool, the description is sufficiently complete for an agent to select and invoke it 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 0%, so the description must compensate. It does so fully by explaining each parameter: wallet_address format, wallet_signature structure, wallet_timestamp unit, wallet_nonce uniqueness constraint, agent_display_name purpose, and prefix filter with an example. This adds significant meaning beyond the bare 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?

The description clearly states the tool's action: 'List documents in the agent's workspace.' This specifies a verb (List) and a resource (documents in the agent's workspace), distinguishing it from siblings like auteng_docs_recent (which likely lists recent documents) and other mutation tools. The scope is unambiguous.

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 lists documents in the workspace, and the optional prefix filter hints at usage for organizing or filtering. It does not explicitly name alternatives or exclusions, but the list action is self-evident. It also cross-references auteng_docs_create for auth details, which indirectly aids usage.

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