yagames-list-my-games

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

With no annotations, the description carries full burden. It adds the auth env var requirement and clarifies scope, but it does not state whether the operation is read-only, whether pagination applies, or what exact env vars are needed. The verb 'List' implies read-only, but specifics are sparse.

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?

A single sentence conveys the action, scope, and a critical prerequisite without filler. Every word adds value and the core behavior is front-loaded.

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 zero-parameter list operation, the description covers what it lists, whose account it lists, and that auth is required. It does not describe the return format or pagination, but the simple nature and explicit scope make it sufficiently complete for selection and invocation.

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 has zero parameters and no required inputs, so there is nothing for the description to explain. The baseline for no-parameter tools is 4, and the description correctly avoids inventing unnecessary parameter details.

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 ('List') and identifies a precise resource ('all games uploaded to your developer account'). The 'my games' scope clearly separates it from siblings like yagames-search or yagames-popular.

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 clearly states an auth prerequisite and establishes the tool is for the developer's own games. However, it does not explicitly mention when to choose this over yagames-search or other siblings, leaving the decision partly inferred from the name.

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