get_recent_checklists

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the tool returns subId and focuses on recent checklists, but does not clarify parameter combinations (hotspot vs region vs lat/lng) or the time window for 'recent.' Some useful behavior is disclosed, but significant gaps remain.

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 three sentences, each earning its place: it states the purpose, explains the return value, and gives a prerequisite. No redundant or extraneous information.

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?

Given the tool has 5 optional parameters and no output schema, the description provides partial context: it mentions the subId return and prerequisite, but doesn't specify whether hotspot and region parameters are mutually exclusive or what the default time range is. This leaves some ambiguity for an agent deciding how to invoke the tool.

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 descriptions already cover all 5 parameters at 100%, so the baseline is 3. The tool description adds value by linking hotspot ID usage to resolve_hotspot, which helps with the locId parameter. It does not elaborate on other parameters but provides a practical hint.

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's function with a specific verb and resource: 'Get recent checklists submitted at a hotspot or in a region.' It also distinguishes itself from the many observation-focused sibling tools by mentioning it returns subId for use with view_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?

Provides clear usage context by noting the return value can be used with view_checklist and advising to 'Use resolve_hotspot first if you only have a hotspot name.' This gives an explicit prerequisite and downstream use, though it does not explicitly mention alternatives like get_recent_observations.

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