find_tasks

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

No annotations are provided, so the description must disclose behavioral traits. It indicates the tool is read-only and lists tasks from a specific list, but does not detail return format, pagination, or permissions. The hardcoded list name 'Burrows Ops' is a behavioral clue.

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 a single sentence with a parenthetical, concise and front-loaded. However, the parenthetical could be clearer and the structure slightly muddled.

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 no output schema and no annotations, the description leaves gaps: it doesn't specify sorting, result limits, or what fields are returned. The presence of an undocumented 'listName' parameter further reduces completeness.

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 0%, so the description must explain parameters. It partially documents the 'status' parameter with three possible values (notStarted, inProgress, completed) but does not mention the 'listName' parameter at all, which is confusing given the description implies a fixed list.

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 'List tasks in the "Burrows Ops" list' with a specific verb and resource. Also clarifies its use for resolving a task id before completing, distinguishing it from sibling tools like complete_task and create_task.

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 says to use this tool to resolve a task id before completing it, and mentions an optional status filter. However, it does not specify when not to use it or provide alternatives beyond the sibling tools.

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