cpu_list_my_lots

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

With no annotations provided, the description carries the full burden. It discloses 'Requires a session', which is a key behavioral requirement, and notes that it covers 'all lifecycle states' with optional filtering. This adds useful context beyond the schema, though it does not describe behavior when no session exists.

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, front-loaded with the core function, and includes the important session requirement and use case without any fluff. Every sentence earns its place.

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 simple one-parameter list tool with no output schema, the description covers purpose, ownership scope, optional filter, session requirement, and an explicit use case. It implies the return includes lotIds, which is the main need. A minor gap is lack of detail on exact return structure, but that is not critical.

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 100%, with the `state` parameter fully documented including enum values and default. The description adds only 'optionally filtered by `state`', which duplicates the schema. Baseline 3 is appropriate given the high schema coverage.

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' with a clearly scoped resource 'the lots you have created', distinguishing it from sibling tools like cpu_list_lots which presumably lists all lots. It also mentions lifecycle states and optional filtering, making the purpose unambiguous.

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?

It explicitly states when to use the tool: 'Use this to find your lotIds and track create / cancel progress.' The scope 'you have created' implies an alternative for viewing others' lots, but it does not name a specific alternative or explicitly state when not to use it. Still, clear guidance is provided.

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