filter__update

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

With no annotations, the description carries the burden of disclosing side effects and behavior, but it only restates the high-level purpose. It does not mention persistence, scope, whether the update replaces or merges the existing filter, or what happens when no parameters are provided.

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 short and front-loaded with the operation and resource. The two clauses are mostly non-redundant, one naming the action and the other clarifying the intent, though the category prefix and phrasing could be tighter.

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?

The tool has nuanced update semantics and no output schema, but the description does not clarify whether omitted parameters keep previous values or clear them, nor does it describe the response or effect on the current visibility filter. The schema covers parameter meanings but not operational behavior.

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 description itself adds no parameter-level detail, but the input schema has 100% coverage with clear descriptions and examples for all three parameters. The schema already explains the meaning of excludeServers, excludePatterns, and includePatterns, so the baseline of 3 is appropriate.

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 action ('Update') on a clear resource ('tool visibility filter') and explains its effect ('control which tools are visible to AI'). It is distinguishable from siblings like filter__get and filter__reset by the update operation, though it does not explicitly name or contrast them.

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?

There is no guidance about when to use this tool versus alternatives such as filter__get or filter__reset. The purpose implies it should be used when adjusting tool visibility, but no explicit context, prerequisites, or exclusions are provided.

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