list_tasks

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

Discloses index-backed for performance, lists return fields, and implies read-only nature. Lacks explicit statement about side effects, but no annotations to contradict. Solid for a read 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?

Two sentences efficiently convey purpose, output format, and scoping. No wasted words.

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?

Explains return structure, status values, and scoping well. Could mention pagination parameters (limit, offset) more explicitly, but overall sufficient given complexity.

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% with adequate descriptions. Description adds slight context (status values listed, scoping phrasing) but does not significantly enhance understanding beyond 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?

Clearly states the tool lists checkbox tasks as structured rows with specific fields (path, text, status, etc.). Distinguishes from siblings by focusing on tasks rather than general notes or files.

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?

Describes scoping options (folder, tags, where, match, status) and implies use for filtered task listing. Does not explicitly say when not to use or compare to siblings like search_notes.

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