waiaas_pm_get_pnl

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the summary includes realized/unrealized PnL, time periods, or data freshness. The agent cannot infer important behavioral details.

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 sentence, concise and front-loaded with the action. It avoids unnecessary words, though it could be slightly more informative without sacrificing conciseness.

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 and no annotations, the description is too sparse to fully inform the agent. It lacks details on the PnL summary contents (e.g., time period, breakdown) and potential error conditions, making the tool underspecified for an AI agent.

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 wallet_id has a schema description of 'Auto-resolved for single-wallet sessions', which adds useful context beyond the raw schema. The description itself complements the schema by hinting at automatic resolution.

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 clearly states 'Get Polymarket profit and loss summary for a wallet', specifying the exact resource (PnL summary) and platform (Polymarket). This distinguishes it from sibling tools like waiaas_pm_get_balance or waiaas_pm_get_positions.

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 implies the tool is for fetching PnL summaries, but it does not explicitly state when to use it over alternatives (e.g., get_positions) or mention prerequisites like needing a session. Usage context is implicit.

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