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

With no annotations, the description carries the burden of disclosing behavior. It lists the return fields, which is helpful, and 'browse' implies read-only. However, it doesn't mention pagination behavior, ordering, or any potential side effects, though for a read-only gallery tool the risk is low.

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?

A single sentence effectively communicates purpose and return data. No filler or redundancy. The verb appears first, followed by the resource and key fields, making it 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 simple read tool with only two parameters and no output schema, the description is largely sufficient. It names the resource and the fields returned. It could be more complete by stating the return shape (array of objects) or pagination behavior, but those are partially inferable from the schema.

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 coverage is 100%: limit and offset each have descriptions including defaults and bounds. The description adds nothing beyond the schema, as 'recent' hints at ordering but doesn't define it. Baseline of 3 is appropriate when the schema already documents parameters fully.

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 purpose: browsing recent looksmaxxed burns and listing the specific data fields returned (IPFS URLs, addresses, timestamps, token IDs). The verb 'browse' implies a read-only list operation, and the resource is well-defined. It is distinct from siblings like get_activity_feed, though it doesn't explicitly name alternatives.

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 usage is implied by the description: use when you need to browse recent looksmaxxed burns. However, it provides no explicit guidance on when to use this over related tools like get_activity_feed or get_nft_inventory, and lacks any exclusions or contextual prerequisites.

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