Advanced Search Work Items

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

With no annotations provided, the description carries the behavioral burden. It discloses that the endpoint is permission-gated on some workspaces/editions and that it may return 403, which is valuable beyond the schema. It doesn't describe return format or side effects, but 'search' strongly implies a read-only list 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?

Three short sentences, front-loaded with the core purpose, followed by a relevant capability note and a fallback. Every sentence earns its place and there is no filler.

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?

For a 5-optional-parameter search tool with no output schema, the description is quite complete: it explains the advanced filtering nature, the permission caveat, and fallback alternatives. It could mention what kind of result shape to expect, but the sibling context and name make the return type reasonably inferable.

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%, so the baseline is 3. The description adds some semantic meaning by noting that the filters object is supported in addition to a text query, but it does not elaborate on filter structure or parameter relationships beyond what the schema already states.

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 states a specific verb and resource ('Filtered work item search') and immediately keys in on the differentiator: it uses Plane's advanced-search endpoint with a structured filters object plus a text query. It clearly distinguishes itself from simpler siblings by name and behavior.

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 explicit when-to-use context: structured filters are supported in addition to a text query. It also provides a concrete fallback instruction — if the endpoint returns 403, use search_work_items or list_work_items — which is direct, actionable guidance.

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