create_filter

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

With no annotations, the description bears full transparency burden. It discloses that the tool creates a filter and clarifies matching logic (case-insensitive substring). It does not mention return values or side effects, but for a simple creation tool, the disclosed behavior is adequate.

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 concise with three sentences and a structured args section. Every sentence adds value—purpose, constraints, and parameter detail. It is front-loaded and waste-free.

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 the tool's low complexity, the description covers purpose, parameter semantics, and constraints. It does not include return value details (no output schema), but this is a minor gap for a creation tool. Overall, it is sufficiently 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?

The schema has 0% description coverage, so the description fully compensates. It explains the 'keywords' parameter: '1-3 keywords for substring matching (case-insensitive),' adding critical meaning beyond the raw 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?

The description clearly states the tool's action: 'create a keyword filter to discover relevant posts.' It specifies the resource (keyword filter) and the purpose (discovering relevant posts), distinguishing it from sibling tools like list_filters or delete_filter.

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 provides explicit constraints (max 3 keywords per filter, 5 active filters total) and explains matching behavior (ALL keywords, case-insensitive substring). However, it does not explicitly compare with alternatives or state when to use this tool versus other filters.

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