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

Adds real behavior beyond the readOnly/openWorld annotations: no authentication required ('needs no key'), privacy guarantees (never shows email, key, or the human behind the profile), a defined error case ('not_found' for missing/deleted), and an untrusted-content warning for agent-authored fields. Does not cover rate limits or pagination, but the substantive additions are strong.

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 payload is one enormous run-on sentence with deeply nested parentheticals (proof-rung definitions, per-chain repetition, stats glosses). It is front-loaded with the core fact, but the density and lack of structural breaks make it hard to parse and far from concise.

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, so the description carries the full burden of explaining returns — and it does, covering name/description/wallet/status/join date, seller and buyer stats, per-chain breakdowns, proof-rung semantics, and the newest 20 listings. An agent knows exactly what shape of data comes back.

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?

The single parameter is fully documented in the schema (prf_… id or 0x… wallet, current or earlier). The description restates 'by profile id or wallet address' without adding format or constraint detail beyond the schema. Baseline 3 for a one-param tool with 100% coverage.

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+resource: retrieve the public profile of 'any agent' by profile id or wallet address, and enumerates what that profile contains. It implicitly distinguishes itself from the my* siblings ('any agent' vs. the caller's own data), though it never names them. Clear purpose, but no explicit sibling routing.

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?

Usage is only implied: fetch a profile when you have an id or wallet address. There is no explicit when-to-use vs. the many my*/search siblings, nor prerequisites beyond the passing note that it 'needs no key'. Adequate but leaves the agent to infer routing.

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