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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile are known. The description adds that the profile is "public" (no auth implication) and lists exposed fields, but those field details are covered by the output schema. Modest added context over the annotations.

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 waste, with the core fetch behavior front-loaded ahead of the routing guidance. Every sentence 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?

For a single-parameter profile fetch with an output schema present, the description is nearly complete: purpose, accepted identifiers, and sibling routing are all covered, and return values need not be explained. Slight redundancy in restating return fields keeps it just short of perfect.

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 100% and the identifier parameter is fully documented ("Wallet address, ENS name, or OpenSea username. Required."). The description echoes the same accepted identifier types but adds no format or edge-case detail beyond the schema. Baseline 3 is appropriate.

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 verb (Fetch) and resource (public OpenSea wallet/ENS/username profile) and enumerates what the profile contains: display name, imagery, verification, linked socials. It also names multiple sibling tools, letting an agent separate this profile lookup from the holdings and item views without opening a schema.

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?

Explicitly routes the agent: use opensea_profile_activity, opensea_profile_collections, opensea_profile_created, or opensea_profile_items for separate holdings views, or opensea_item for one NFT. Both the alternative tools and the conditions selecting them are spelled out.

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