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

No annotations are provided, so the description carries the full burden. It does disclose the HMAC authentication requirement and lists the return categories, which adds context. However, it does not explicitly state whether this is a read-only operation, describe error handling for unknown users, or mention data sensitivity—leaving some behavioral traits undisclosed.

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?

The description is a single, well-structured sentence that packs in the purpose, the specific profile components, and the authentication requirement without any filler. Every phrase 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?

With no output schema, the description must convey what the tool returns, and it does so by listing the profile dimensions. It also includes the auth prerequisite. It could be more complete by mentioning error behavior or confirming read-only nature, but it sufficiently covers the essentials for a simple lookup tool.

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% because the only parameter (userId) is described as 'email or wallet address'. The description adds no additional semantic detail about the parameter beyond what the schema already says, so it stays at the baseline.

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 uses a specific verb ('Get') and clearly identifies the resource ('user's behavioral profile'), then enumerates the distinct components (earn patterns, persona archetype, tag/brand affinities, price preferences, network position). This distinguishes it from sibling tools like user_stats and user_balance.

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 description clearly implies when to use it: when you need a behavioral profile rather than numerical stats or simple balance. It also notes the HMAC authentication prerequisite. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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