quire.searchFolderTasks

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

Annotations provide readOnlyHint: true and openWorldHint: true, indicating a safe read operation that may return incomplete results. The description adds no behavioral details beyond the schema (e.g., pagination, rate limits, response format). It does not contradict annotations.

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, front-loaded sentence that efficiently conveys the tool's purpose. While brief, it contains no redundant information and is appropriately concise for the tool's simplicity.

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?

Despite having 6 parameters and no output schema, the description does not explain the return format (e.g., a list of task objects) or how results are limited. Given the openWorldHint and the existence of sibling list tools (e.g., quire.listTasks), the description leaves the agent with insufficient context about what to expect from the search.

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%: all parameters (folderId, keyword, status, priority, assigneeId, tagId) have descriptions in the schema. The tool description merely summarizes 'by keyword and optional filters', adding no new semantic information beyond what the schema already provides.

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 'Search for tasks within a specific folder by keyword and optional filters.' It specifies the verb (search) and the resource (tasks within a folder), effectively distinguishing from sibling tools like quire.searchTasks (which likely searches all tasks) and quire.searchOrganizationTasks (organization-wide).

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 implies usage for folder-scoped keyword search with optional filters, but does not explicitly state when to prefer this over quire.searchTasks or quire.searchOrganizationTasks. No exclusions or alternative recommendations are provided, yet the context is clear enough for an informed agent.

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