seerr_list_settings_cache

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

Annotations already declare readOnlyHint=true. The description aligns with this and adds a small qualifier ('active') but provides no additional behavioral context such as what constitutes an 'active' cache or whether any side effects occur. It neither contradicts annotations nor adds substantial transparency.

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 a single, front-loaded sentence with no superfluous words. It fully states the tool's purpose in minimal text.

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 has no parameters and an output schema exists, the description is largely sufficient. However, 'active caches' could be more specific (e.g., memory vs. DNS caches), but the sibling tools and context reduce ambiguity. Overall, it meets the needs for a simple list tool.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and the term 'active' adds a slight semantic filtering nuance but is not parameter-related.

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 'Get a list of active caches' clearly states the verb (Get list) and resource (active caches), distinguishing it from siblings like seerr_flush_cache and seerr_flush_dns_cache which are about clearing caches.

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 implies when to use this tool (to list active caches) but does not explicitly mention alternatives or exclusions. It does not say 'use this to inspect cache state' or contrast with flush_cache, leaving usage context implicit rather than explicit.

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