get_my_pnl

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

No annotations are provided, so the description carries the full burden. It discloses the returned information (earnings, rewards, fees, etc.) but does not mention whether the operation is read-only, any authentication requirements, rate limits, or the default period when 'since' is omitted. These gaps reduce transparency for an AI 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 sentences: the first states the primary purpose, the second lists key components. It is front-loaded and contains no unnecessary words or repetition.

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 compensates by listing the components of the P&L breakdown (A2A earnings, rewards, fees, gas costs, etc.), which is helpful. However, it does not specify the default behavior when 'since' is omitted (e.g., last 30 days) or the time granularity. This is a minor gap for completeness.

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 schema already describes the single optional parameter 'since' with a clear description. The tool description does not add additional meaning beyond what the schema provides. With 100% schema coverage, a score of 3 is appropriate.

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 the tool fetches the agent's profit and loss breakdown. It lists specific components (A2A earnings, rewards, fees, etc.) which differentiates it from sibling tools like get_defi_rates or get_agent_trust_report. The verb 'fetches' and resource 'PNL breakdown' are specific.

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 says 'Use this to inspect...' which implies when to use it. However, it provides no explicit exclusions or alternatives. Given the diverse set of sibling tools, the guidance is adequate but lacks when-not-to-use context.

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