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

Beyond the read-only annotations, it discloses important behavior: username matching prefers exact matches and falls back to the closest public profile with explanatory text. It also clarifies that the data is public on-chain data and does not identify wallet controllers, which is valuable operational context.

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 front-loaded with the primary usage condition and then lists accepted inputs and return contents. It is longer than necessary in places, but the examples and matching caveat are relevant to correct invocation.

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?

Given the single well-documented parameter, rich annotations, and an output schema, the description is complete enough for an agent to select and call the tool correctly. It covers accepted inputs, return contents, matching behavior, and key limitations.

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%, so the parameter is already documented. The description still adds useful semantics by restating accepted identifier formats and explaining the exact-vs-fallback username matching 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?

The description states a specific verb and resource: it retrieves a Polymarket trader profile from a wallet, URL, or username. It is clear about what it does, but does not explicitly differentiate itself from the sibling get_trader_positions tool, even though it returns a limited positions summary.

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?

It gives concrete user-intent examples for when to use the tool, such as asking about a wallet, a profile link, or a username. However, it does not explicitly say when to prefer alternatives like get_trader_positions for deeper position data.

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