filter_projects

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

Discloses that the API does not support ad-hoc sort, explains the monotonic ID workaround, and notes conditions are ANDed. No annotations, but description covers key behaviors; lacks mention of error handling or rate limits.

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?

A single paragraph that is front-loaded with purpose and usage, no fluff, every sentence adds value.

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 moderate complexity, the description is thorough: covers filter logic, sorting workaround, and provides a reference link. It feels complete for an agent to use the tool correctly.

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?

Despite 50% schema coverage, the description adds extensive detail on the conditions parameter with field, operator, value examples and a link. The embed parameter is briefly explained, but page and perPage are left to schema defaults. Overall adds significant meaning.

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 it filters projects by structured conditions and contrasts with list_projects, giving concrete examples like 'most recent project' and 'projects opened this month'.

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 when to use this tool instead of list_projects and provides a workaround for the lack of ad-hoc sort using monotonic IDs.

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