soundiiz_cache_invalidate

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

No annotations provided. Description only states it invalidates cache and defaults scope, but does not disclose side effects, performance impact, or whether invalidation affects other users or sessions.

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?

Single sentence, front-loaded with key action and default. No unnecessary words.

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 simple cache invalidation tool with no output schema, the description lacks details on return value, error handling, and behavior when id is specified. Given no annotations, it feels incomplete.

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 0%. Description only mentions scope default but does not explain the 'id' parameter or the meaning of each scope value (beyond 'all'). Agent would need to infer id's purpose.

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 verb 'Invalidate' and resource 'cached responses', and specifies default scope. It distinguishes from sibling tools which are auth, read, write operations on different resources.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, when not to use, or comparison with similar tools like soundiiz_auth_clear.

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