get_checklist

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

With no annotations provided, the description carries the burden for behavioral disclosure. It explicitly marks the tool as 'introspection only', notes the version pinning behavior, and warns about duplicated rubric payloads when called alongside assess_manuscript. It does not explicitly state that it makes no modifications, but 'introspection only' strongly implies a read-only operation.

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 front-loaded with the core purpose and content details, followed by a useful usage warning. It is slightly longer than strictly necessary because the second paragraph restates the optionality that earlier wording implies, but every sentence contributes actionable information and there is no fluff.

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 single-parameter, no-annotation, introspection tool, the description covers what the tool returns, how the version parameter works, and how it relates to the assess_manuscript flow. The presence of an output schema reduces the need to describe return structure. It does not discuss relationships to render_checklist siblings, but the word 'encoded' and the detailed content list make the tool's role reasonably clear.

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 schema provides a 'version' parameter with a default but no description, and schema coverage is 0%. The description compensates by explaining the parameter's meaning: 'Pass a version id to pin; omit for the current default.' This is sufficient for selecting a version, though it does not enumerate valid version values or formats.

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 names a specific verb and resource ('Return the encoded TARGET checklist spec') and enumerates the exact content of the spec: 39 leaf subitems, 21 published items, intents, notes, signal terms, pairing links, and applicability rules. It also differentiates from assess_manuscript by clarifying that get_checklist is for standalone inspection, not an assessment prerequisite.

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 explicit when-to-use and when-not-to-use guidance: it is 'OPTIONAL in the review flow', 'introspection only', and should not be combined with assess_manuscript because that already embeds the rubric. It closes with a direct instruction: 'Use this when you want to inspect the spec on its own, not as a required step before assessing.'

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