checklists

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond them: the output composition (tailored list plus buying-guide links) and the fact that input items are filtered/excluded rather than mutated. It does not mention behavior for unknown activities or empty result sets, keeping it short of a 5.

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?

Two sentences, zero waste. The core behavior is front-loaded and the usage router is placed last where it belongs.

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 the description compensates by stating what is returned (tailored list plus buying-guide links). Combined with 100% schema coverage and annotations, an agent has everything needed to call it correctly; only edge-case behavior is unaddressed.

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 coverage is 100%, so the schema already documents all four parameters, including the activity enum and the loose-match exclusion rule. The description restates the parameter effects in workflow order but adds no syntax or format detail beyond what the schema provides, which is the expected baseline of 3.

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?

Names a specific verb+resource ('build a customised packing list') and enumerates the transformations it performs (start from activity, filter categories, exclude, add). The final sentence explicitly routes the agent away from the full standard checklist, distinguishing it from get_checklist.

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?

States the trigger condition clearly: 'Use this when the user wants a list shaped to their specific trip rather than the full standard one.' The alternative (the standard checklist, presumably get_checklist) is implied rather than named, and no explicit when-not condition is given, but the routing intent is unambiguous.

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

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, but the description adds real behavioral context: tents come back best-scored first, tent searches default to car camping unless backpacking is signaled, and absent budget data must be acknowledged rather than guessed. The presentation rules (lead with top pick by exact name; say 'rates'/'scores' not 'tested'; use only returned data) go well beyond annotations. Loses a point because it does not describe pagination or what the 'guides' payload actually looks like at a structural level.

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?

Front-loaded with the core search behavior, then operational rules. Every sentence carries a distinct instruction. It is dense and runs long, but each clause earns its place (branching logic, defaults, phrasing constraints, missing-data handling). Slightly heavy for a single tool description.

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 an open-ended, seven-parameter, zero-required search tool with no output schema, the description covers the full operational surface: domain split, query semantics, defaults, missing-data behavior, and result-presentation contract. Nothing an agent needs to call and present results correctly is missing.

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 coverage is 100% so baseline is 3, but the description adds genuinely non-obvious semantics the schema does not state: filler words like 'best' are ignored, plain-word queries are parsed for capacity/seasons, and the car-camping-vs-backpacking default. These are behavioral parameter rules that meaningfully improve invocation accuracy beyond the schema's own text.

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 (Search) and resource (Wilderness Times' gear recommendations), then splits the domain into two clearly-defined behaviors: tents scored out of 10, and everything else returned as buying guides. This is far more specific than any sibling (get_gear, build_checklist), so an agent can distinguish it without opening a schema.

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?

Explicitly names trigger conditions ('whenever someone asks what gear to buy, which tent suits a trip, or for a recommendation'), a no-arg fallback ('call with no query to see what is covered'), and a specific decision procedure ('if group size matters and the user has not given it, ask before recommending'). The tent vs. guide branching is stated as an operational rule, not left to inference.

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the result is category-organised and includes buying-guide links, and lists can exceed 100 items, which explains why filtering matters.

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?

Three sentences, front-loaded with what the tool returns, then usage, then input flexibility. No waste, though the natural-phrasing sentence partly repeats the schema's own note.

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?

With no output schema, the description carries the burden of describing the return shape (categorised checklist with guide links) and does so. Combined with complete annotation coverage, an agent has enough to call it correctly; only the relationship to sibling checklist tools is unstated.

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% and the schema already documents both params, including that common phrasings are accepted. The description's note about natural phrasing and the '100+ item list' rationale for narrowing is a marginal add over what the schema 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?

States a specific verb and resource ('Get a full ... packing checklist for one activity'), plus scope (organised by category, with buying-guide links). It implicitly separates itself from list_checklists and build_checklist via the 'one activity / full checklist' framing, but never names a sibling explicitly, so differentiation is left to inference.

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?

'Use this whenever someone asks what to pack for a trip' gives a clear triggering condition. There is no when-not guidance or mention of the alternatives (build_checklist, get_checklist_pdf), so an agent must infer the boundary itself.

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

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

Annotations already establish readOnly, idempotent and non-destructive behavior, so the bar is lower. The description adds genuinely new context: the output is the standard unedited list regardless of user customisation, it is free with no signup, and it is explicitly contrasted with the customisable share_checklist path. It stops short of saying whether the return is a file, bytes or a URL.

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?

Front-loads what the tool returns, then the scope caveat, then the alternative — three sentences with no filler. The IMPORTANT marker correctly flags the sentence an agent must not miss, and nothing is repeated from the schema or annotations.

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 one-parameter read tool with full annotation coverage and no output schema, the description covers scope, eligibility and routing completely. The only gap is the shape of the return value (file, stream or download link), which matters for a PDF-producing tool but is not stated.

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 coverage is 100%, making 3 the baseline, but the description goes further by enumerating the valid activities (camping, backpacking, winter camping, day hiking) where the schema has no enum and only says 'Activity whose PDF to return.' That enumeration is real added value for a required parameter.

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?

Names a specific verb and resource ('Get the STANDARD published Wilderness Times checklist as a ready-made PDF') and immediately bounds the scope to the unedited published list. It also enumerates the supported activities, letting an agent confirm eligibility without opening the schema.

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?

Explicitly states the condition that selects the sibling: if the user has added, removed or filtered items, call share_checklist instead. It even explains what that alternative returns (a builder link with PDF/Excel/Sheets/print export), so routing is unambiguous.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description goes beyond them by detailing the returned payload and the tent-only fields that may or may not appear. It stops short of stating anything about failure modes (e.g., invalid or stale id) or that results are a single item, not a list.

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?

Front-loaded with the verb and scope, and both sentences carry real information. The first sentence is long and clause-heavy, but each clause identifies a distinct returned field rather than padding, so it stays justified.

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, so the description must carry the return-value burden, and it does — naming the review summary, specs, pros/cons, stockists, and the conditional tent fields. Combined with complete parameter docs and annotations, an agent has everything needed to call it and set user expectations.

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 coverage is 100% and both parameters are documented in the schema, including the enum and the advice to pass kind. The description only reinforces the provenance of id ('one item from find_gear') without adding format or edge-case detail, so the baseline 3 applies.

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 (get) and resource (gear details) and enumerates exactly what is returned: review summary, specs, pros/cons, retailers, plus tent-specific extras. It explicitly frames itself relative to find_gear, so an agent can separate it from that sibling without reading either schema.

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?

Gives explicit when-to-use conditions: after find_gear when the user narrows to one item, wants a detailed two-item comparison, or wants alternatives to a tent. It names the prerequisite tool (find_gear) and even prescribes how to present alternatives (one sentence on the key tradeoff).

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context by disclosing that the catalog is a fixed set of exactly 11 activities, which tells the agent the result space is closed and bounded.

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?

Front-loaded with the action, followed by the routing cue. The enumeration of all 11 activities is long but functionally earns its place by letting the agent match free-text user descriptions to a valid activity name.

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 no-parameter, no-output-schema listing tool with full annotation coverage, the description supplies everything needed: what is returned, its scope, and when to reach for it. Nothing required for correct invocation is missing.

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 takes no parameters (0 required, 0 total) with 100% schema coverage, so the schema leaves nothing to explain. Baseline 4 applies; there is no parameter meaning for the description to add or omit.

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 every Wilderness Times packing checklist available') and quantifies the scope with the full activity catalog. An agent can immediately distinguish it from get_checklist, build_checklist, and get_checklist_pdf.

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?

'Call this first if you are unsure which activity matches what the user described' gives an explicit selection condition and ordering relative to the other tools. It stops short of naming which sibling to use once the activity is known, but the context is clear.

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds real context beyond that by describing the artifact produced (a live builder link where items tick off, exports to four formats, gear links preserved). It does not say whether the link persists, expires, or is stored server-side, which is the remaining behavioral gap.

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?

Outcome and trigger condition are front-loaded in two sentences with no filler paragraphs. Sentence one is dense and carries mild promotional weight ('free Wilderness Times checklist builder'), but every clause conveys usable information about the returned artifact.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so well by describing the link and its capabilities. The only omission is the lifecycle/durability of the link and its relationship to list_checklists, which an agent might reasonably wonder about.

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 coverage is 100% and every parameter carries its own description, so the baseline is 3. The description adds a cross-tool semantic link — 'takes the same arguments as build_checklist, so you can share whatever you just built' — which tells the agent it can pass a just-built spec through unchanged, a genuine plus over 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 ('Turn a checklist into a link') and goes further by describing what the resulting link does (opens in the builder, tick-off, export to PDF/Excel/Sheets/print). It distinguishes itself from get_checklist_pdf and build_checklist by scoping to the user's tailored list.

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?

Gives an explicit trigger set: 'whenever someone has customised a list, or asks to save, share, print, download or get a PDF of THEIR list.' The cap is on 'THEIR' vs. the base-list siblings, and it explicitly tells you to reuse build_checklist arguments, but it never names an exclusion against get_checklist_pdf even though it claims PDF output — a gap given a PDF-specific sibling exists.

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