Clear Cache

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

The description indicates a mutation operation ('clear cached data'), but annotations include readOnlyHint: true, which contradicts the described behavior. No additional behavioral context is provided beyond the contradictory annotation.

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?

Two efficient sentences: first states purpose, second provides usage context. No wasted words, front-loaded with key information.

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?

With one optional parameter, no output schema, and clear usage instructions, the description is adequate. It could mention potential side effects or confirmation prompts, but the given context is sufficient for most agents.

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 100% with the 'scope' parameter having an enum and description. The tool description does not add extra meaning beyond what the schema already provides, so baseline score of 3 applies.

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?

Description clearly states the verb 'clear' and the resource 'cached e-arveldaja API and reference data'. It also provides two specific use cases, distinguishing it from sibling tools that deal with accounting data rather than cache management.

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 states when to use the tool: after changing data in the web UI or before reports needing latest state. This provides clear guidance and implicitly suggests when not to use it (e.g., during normal operations).

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