list_my_lots

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 requirement for a session and the behavior of listing across all lifecycle states with optional filtering. While it does not mention pagination or return format, these are common for list tools, and the description provides adequate context for safe invocation.

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?

Two concise sentences, each focused and informative. No fluff, no repetition, and key information is front-loaded (action, resource, scope). 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?

Given the simplicity of the tool (1 optional parameter, no output schema, no annotations), the description covers purpose, usage, and a prerequisite. It could optionally mention the return structure, but the stated goal ('find your lotIds') implies the output, making it fairly complete.

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 coverage is 100% (one parameter with a thorough description). The tool description restates the purpose of the 'state' parameter as an optional filter, which adds minimal value beyond the schema. Per guidelines, a score of 3 is appropriate when schema already provides sufficient detail.

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 verb (list), resource (lots), and scope (you have created, across all lifecycle states). It distinguishes from the sibling tool 'list_lots' by specifying ownership, making its purpose highly specific and non-ambiguous.

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 provides explicit usage guidance: 'Requires a session. Use this to find your lotIds and track create / cancel progress.' It implies when to use this tool (finding own lots) versus siblings like 'list_lots', though it does not explicitly state exclusions.

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