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

There are no annotations, so the description carries the full burden, but it does not disclose address validation, network requirements, data freshness, or failure behavior. The verb 'Get' weakly implies a read operation, but no explicit behavioral guarantees or caveats are provided.

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?

One front-loaded sentence with no filler; it names the verb, resource, and key output dimensions immediately. Every word earns its place.

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?

Adequate for a simple single-parameter read tool: the core input and output dimensions are inferable. But with no annotations, no output schema, and no sibling comparison, an agent still lacks guidance on address format and when to use this tool instead of related Zora tools.

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?

With 0% schema description coverage, the description provides some meaning by tying the sole parameter to a wallet's Zora holdings and PnL. However, it does not specify the expected address format (e.g., 0x-hex vs ENS) or any constraints, so compensation for the empty schema is only partial.

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?

States a specific action ('Get wallet holdings') on a specific resource ('Zora') and names the output dimensions ('PnL and allocation breakdown'). This clearly distinguishes it from siblings like holder_analysis or zora_rug_check, which focus on token holders or safety checks rather than a single wallet's portfolio.

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?

No guidance is given about when to prefer this tool over its siblings or what preconditions apply. The description only implies use for wallet portfolio lookups; it never names alternatives or exclusion criteria.

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