List listing drafts

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

With readOnlyHint=true in annotations, the safety profile is covered. The description adds value by disclosing sort order ('newest first') and that returned fields include status and headline. It does not mention pagination or filtering behavior, but the annotations lower the bar and the added details are useful.

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, well-structured sentence that front-loads the core purpose ('Lists local drafts') and packs in ordering and output details without waste.

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 list tool with two optional parameters and no output schema, the description conveys the main purpose, ordering, and key fields. It is slightly incomplete in not explaining the effect of the 'limit' parameter or whether pagination exists, but overall it is sufficient for basic usage.

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 only 50%: the 'status' parameter has a description, but 'limit' does not. The tool description does not mention parameters at all, instead focusing on output fields. It fails to compensate for the undocumented 'limit' parameter, offering no guidance on its meaning or constraints.

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 tool 'lists local drafts' with a specific verb and resource. It also distinguishes itself from siblings like get_listing_draft by focusing on the collection, and adds sorting ('newest first') and output fields ('status and headline fields').

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 context is clear: this is for listing local drafts, which is distinct from single-draft tools like get_listing_draft or mutating tools like delete_draft. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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