Agent positions

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

No annotations are provided, so the description carries the full disclosure burden. It doesn't state that the call is a safe read, whether it requires an active session or authentication, how 'recent matches' is scoped, or whether results are paginated. Only a vague topical hint is given.

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?

It is a single short sentence with no filler, which is good. But it is a loose noun phrase rather than a front-loaded statement of action, and it packs two loosely related concepts (balance, match outcomes) without a lead verb, making it slightly harder to parse than it needs to be.

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 annotations and no output schema, the description is the only source of information about what comes back, and it is too thin: 'recent matches' has no time window, no field list, and no indication of whether results are per-match or aggregated. An agent calling this blind has little idea what to expect.

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 input schema has zero parameters, so there is nothing for the description to clarify; the baseline of 4 applies. No parameter meaning is added or needed.

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 names two things the tool surfaces (portfolio balance and Win/Lose units) which gives a rough sense of a read-only positions view. However, 'Win/Lose units held on recent matches' is domain jargon that isn't defined, and it never distinguishes this tool from the sibling icare_wallet, which presumably also reports balance. Purpose is implied rather than crisply stated.

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?

There is no indication of when to call this tool, what precondition triggers it, or how it differs from icare_wallet or icare_live_matches. The agent is left to guess the relationship between a 'wallet' and 'positions' on its own.

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