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

Annotations already cover read-only and closed-world behavior, so the description's added value is in disclosing the return payload, including the four 'permanent copies' (Ethereum token, Arweave metadata, Arweave HD image, IPFS original) — useful context given no output schema exists. It does not mention failure behavior when neither identifier resolves to a piece.

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?

Two sentences, zero filler. The resource and returned fields come first, and the invocation rule is front-loaded in a short trailing clause.

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?

With no output schema, the description does the necessary work of listing the returned fields so the agent knows what a call yields. It is nearly complete for a simple lookup; only the behavior on a non-matching or ambiguous identifier is unaddressed.

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%, so the baseline is 3, but the description adds meaning the schema never states: that token_id and collection+number are two alternative lookup paths rather than parameters to combine. That resolves the ambiguity of three all-optional parameters sharing one lookup.

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?

It states a specific verb and resource ('Get one BrainDrops piece') and enumerates exactly what the record contains (name, artist, collection, traits, images, permanent copies), which implicitly separates it from the collection-level and search siblings. It never names an alternative tool explicitly, so sibling differentiation is left to inference.

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 final clause 'Give token_id, or collection + number' tells the agent how to invoke it with two alternative key sets, which is real usage guidance. It stops short of saying when this tool is preferable to get_collection or search_braindrops, and gives no when-not guidance.

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