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

With no annotations, the description carries the full burden. It discloses rate limiting ('Rate limited to 10 shares per wallet per day'), authentication requirements ('Requires EIP-191 wallet signature auth'), and the visibility constraint ('only public in current version'). However, it does not mention side effects like whether shares can be revoked or what happens if the path doesn't exist.

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: purpose and return value first, then rate limit and auth, followed by a clean Args list. Every sentence adds value, and the front-loaded main action makes the tool's intent immediately clear.

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?

The description covers the main action, return value, auth, rate limit, and parameter meanings. An output schema exists, so it need not elaborate on return structure. However, it lacks context on when to use versus alternatives and does not mention potential error behaviors or side effects, leaving some gaps for a tool with 7 parameters.

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 adds meaningful detail for auth parameters (signature format, timestamp type, nonce length and single-use), provides a path example, and clarifies the visibility constraint. This goes well beyond the bare schema titles.

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 'Share a document publicly. Returns a shareable URL.' This uses a specific verb (share) and resource (document), and distinguishes from sibling tools like create, delete, list, update, and publish_markdown by focusing on the sharing action.

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?

Usage is implied by the first sentence, but the description does not explicitly state when to use this tool versus alternatives such as auteng_publish_markdown. It mentions 'See auteng_docs_create for auth details' but that is about authentication, not usage context. No exclusions or alternative guidance is provided.

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