list_drafts

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe return format, pagination, sorting, or what constitutes a 'draft snapshot'. For a listing tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple listing tool and front-loads the essential information.

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 listing tool with no output schema, the description is minimally adequate but could be more complete. It identifies the resource but doesn't describe the return format or any behavioral characteristics. Given the simplicity of the tool (no parameters) and lack of annotations/output schema, it meets basic requirements but leaves room for improvement.

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 tool has zero parameters (schema coverage 100%), so the description doesn't need to compensate for parameter documentation gaps. The baseline for zero parameters is 4, as there are no parameters whose semantics need explanation beyond what the empty schema already indicates.

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 'List all locally saved draft snapshots' clearly states the action (list) and resource (locally saved draft snapshots). It distinguishes from sibling tools like 'list_remote_drafts' by specifying 'locally saved', but doesn't explicitly contrast with other listing tools like 'list_campaign_examples' or 'list_my_published_levels'.

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 no guidance on when to use this tool versus alternatives. While 'locally saved' implies a distinction from remote drafts, there's no explicit mention of when-not-to-use scenarios or comparisons to other listing tools like 'list_remote_drafts' or 'list_my_published_levels'.

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