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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's value-add is the cost/auth disclosure: 'Free, no payment or key; the same answer as the free Ethos API.' That removes a real planning question for the agent. It adds no notes on rate limits or what happens for a nonexistent handle, which keeps it below a 5.

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?

Front-loaded with the core question and resource, then field list, then use cases, then a worked example. The example output blob is long, but it is doing load-bearing work because no output schema exists. Slightly dense prose (the field enumeration runs long) keeps it from a 5.

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?

There is no output schema, and the description compensates fully by showing the complete response shape including nested stats, userkeys format, and field types. Combined with cost/auth disclosure and a sample input, an agent has everything needed to call this single-parameter tool correctly on the first attempt.

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% and the schema already explains 'X handle without the @, or the numeric X account id', so the baseline is 3. The description adds a concrete worked input, {"handle":"ethos_network"}, which adds real value by demonstrating the no-@ convention and confirming the parameter key name in practice.

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 opens with a specific question-form verb phrase and then names the exact resource: 'The Ethos profile for a handle or numeric account id', followed by an enumeration of the fields returned (display name, credibility score/status, wallets, socials, XP, influence factor, review/vouch counts). That input shape ('handle or numeric account id') implicitly separates it from ethos_user_by_address and ethos_search_users.

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?

Three concrete usage contexts are given: vetting an account before engaging, resolving a handle to its wallets, and enriching a mention with reputation. What is missing is explicit routing — it never names ethos_user_by_address as the alternative when you have a wallet instead of a handle, nor ethos_score when only a score is needed, so the agent must infer the boundary.

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