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

No annotations are provided, so the description must carry the full burden of disclosing side effects, read-only behavior, authentication needs, and pagination or limit behavior. It only previews the response shape ('what you put in, and what came back') and does not state whether this is a safe read-only operation or how the `limit` parameter affects behavior.

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 one sentence with no filler and packs meaningful detail about the grouping and data fields. It is slightly awkward as a noun phrase rather than an action-oriented sentence, but it remains compact and readable.

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?

For a tool with no annotations, no output schema, and two undocumented parameters, this description is not complete enough to call confidently. It gives a useful preview of the result structure but leaves the required `owner` parameter, the optional `limit`, and the tool's read-only nature unclear.

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 description coverage is 0%, so the description needed to explain both `owner` and `limit`. It loosely implies the `owner` is the person whose positions are shown via 'you', but it never explains `limit` or how it restricts the result set. This adds minimal semantic value beyond the bare parameter names.

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 identifies the resource being queried: the caller's positions across games, including market stakes and poker seats, broken down per game with capital put in and returned. It lacks an explicit verb like 'list' or 'get' and does not explicitly contrast with siblings such as `my_spaces` or `wallet_summary`, but the core purpose is understandable.

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 gives no guidance on when to use this tool versus alternatives, and it names no sibling tools or exclusion cases. Usage is only implied by the noun-phrase description; an agent has to infer that this is the tool for a position summary.

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