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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and reach are covered. The description adds that only public profile data is returned, which is mildly useful, but says nothing about auth requirements, rate limits, or what happens with an unresolvable identifier.

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 short sentence, identifier forms front-loaded, zero filler. Nothing to trim.

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?

An output schema exists, so return values need not be explained, and the single required parameter is fully covered by the schema. What is missing is only the relationship to the sibling profile tools, which an agent may need to chain correctly.

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 single parameter is already documented as 'Wallet address, ENS name, or OpenSea username. Required.' The description merely restates the same three accepted forms, adding no format examples (e.g. 0x-prefix vs .eth) or resolution-order behavior.

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 resource (OpenSea profile) and enumerates the accepted identifier forms (wallet address, ENS name, username), so the agent knows exactly what entity is fetched. It does not, however, distinguish itself from the sibling profile sub-resources (opensea_profile_activity, opensea_profile_collections, opensea_profile_created, opensea_profile_items), which all take the same identifier.

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?

There is no when-to-use guidance: nothing says this is the base lookup that the opensea_profile_* siblings build on, nor when to prefer it over opensea_search_collections or opensea_item. Usage is only implied by the tool name.

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