get_task_lists

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 explains the return format (id as the CalDAV path segment and display name) and the semantics of 'task lists'. It implies a read-only discovery operation but doesn't explicitly state it or mention edge cases, though the disclosure is sufficiently specific for this simple tool.

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 only two sentences and front-loads the main purpose. Every sentence earns its place: the first states the scope and definition, the second reveals the return fields and a direct usage instruction, with no redundancy or 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?

Given the tool's simplicity (no parameters, no output schema, no annotations), this description is complete. It explains what the tool returns, how to interpret the returned id, and how to use it with related tools. The CalDAV/VTODO context also clarifies the domain without overwhelming detail.

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 has zero parameters, and the input schema is empty, which the description correctly doesn't discuss. The baseline for zero parameters is 4, and the description adds value by explaining the output semantics, which is meaningful given there is no output 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?

The description clearly states the tool's purpose with a specific verb ('Discover') and resource ('all task lists'). It also distinguishes itself from siblings by defining task lists as 'CalDAV calendars that support VTODO' and noting the returned list id and display name.

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 this tool: it provides the necessary list IDs for calling get_tasks or create_task. It doesn't explicitly mention alternatives or exclusions, but the integration with sibling tools is explicit, making the usage scenario clear.

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