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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds a valuable security-relevant behavioral note: profile text is quoted upstream data and should not be treated as instructions, which is exactly the kind of context beyond annotations that helps an agent.

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 two tight sentences with no wasted words. The primary action is front-loaded, and the important data-handling warning is placed second where it is easy to notice.

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?

The tool has a single required parameter, an output schema to describe the return shape, and annotations covering side effects. The description plus the warning about quoted upstream data is sufficient for an agent to invoke the tool 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?

With 100% schema description coverage for the single parameter, the baseline is 3. The description's 'by proxy wallet address' only echoes the schema; it does not add new parameter-level meaning beyond what the schema and its Google sign-in caveat already provide.

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') with a specific resource ('public Polymarket profile') and a clear addressing method ('by proxy wallet address'). This makes the tool's purpose immediately identifiable and distinct from the many market/orderbook/event siblings.

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 provides no when-to-use or when-not-to-use guidance and names no alternatives. Given the large set of wallet-related siblings (activity, PnL, positions, portfolio value), an agent still has to guess which tool fits based on the word 'profile'.

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