Get checklist

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

With no annotations, the description carries the full behavioral burden. It discloses the key branching behavior (one vs. all checklists) and implies a read-only operation through 'Return'. However, it does not mention what happens when an invalid standard id/name is passed, whether results are ordered, or any other side effects or access considerations.

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 front-loads the action and resource, then explains the optional parameter behavior and the intended use case. Every clause earns its place, with no repetition or filler.

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 tool with one optional parameter and simple semantics, the description is sufficiently complete for an agent to select and invoke it correctly. It lacks details about the return structure, but the absence of an output schema and the simplicity of a checklist retrieval make that a minor gap.

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%, so the description adds only marginal meaning beyond the schema: it clarifies that the id is a 'standard id/name' and that omission returns 'every checklist across the library'. This is useful context but largely reinforces what the parameter description already states.

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 a specific verb ('Return'), a specific resource ('compliance checklist(s)'), and the two modes of operation: pass an id/name for one checklist or omit for all. It is distinct enough from the sibling tools (which target 'standards' rather than 'checklists'), though it doesn't explicitly name a sibling alternative.

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 gives clear context for when to use the tool: as a Definition-of-Done gate before shipping, and explains the optional-id behavior. It does not, however, explicitly compare against list_standards, search_standards, or get_standard, so exclusion guidance is only implied by the different resource type.

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