find_duplicate_tasks

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

Description mentions Jaccard similarity and that it checks open tasks, giving algorithmic insight. However, with no annotations, it fails to disclose performance, side effects (none), error handling, or return format, leaving behavioral gaps.

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 concise sentences that front-load the purpose and usage hint. Every sentence is informative with no redundancy.

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?

Lacks description of return value (e.g., boolean or similarity score) and error conditions (e.g., no open tasks). For a simple 2-parameter tool with no output schema, the description should cover these to be complete.

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?

Both parameters are fully described in the schema (100% coverage). The description adds contextual value by explaining the overall purpose but does not enhance meaning of individual parameters beyond the 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 checks similarity of a proposed task against existing open tasks using Jaccard similarity, and explicitly positions it as a pre-creation check. This uniquely distinguishes it from sibling tools like 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?

Directly instructs to call before create_task to avoid redundant work, providing explicit usage context. Lacks mention of when not to use or alternatives, but the sibling set has no directly competing tool.

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