Retrieve available document checklist templates, including built-in starter packages for tax returns, KYC, and mortgage underwriting, to reuse for client intake requests.
List available checklist templates (including starter packages for tax returns, KYC, and mortgage underwriting).
| Name | Required | Description | Default |
|---|---|---|---|
| includeStarters | No | Whether to include built-in starter templates (default: true) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full behavioral burden. It does not state that this is read-only, whether permissions are required, how results are ordered, or whether pagination applies.
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 efficient sentence with the main purpose front-loaded. The parenthetical examples are useful rather than wasteful, though the sentence could also state the read-only nature compactly.
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?
There is no output schema and no annotations, so the description should clarify return shape, ordering, and pagination behavior. It says what is listed but not enough for an agent to know what to expect from the result.
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 single includeStarters parameter is already documented. The description's mention of starter packages adds mild semantic context but no format or default details beyond the schema.
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?
States a specific verb and resource: "List available checklist templates," and the parenthetical names starter-package examples. It is distinguishable from get_template/create_template, though it does not explicitly contrast with get_template.
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?
No guidance on when to use this tool versus get_template or when to omit starter templates. The listing purpose is implied, but there are no explicit conditions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.