pressable_flush_object_cache

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'flush' without explaining side effects, reversibility, required permissions, or impact on site performance. The description lacks any contextual detail about what happens when the cache is flushed.

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 concise sentence that front-loads the verb and object. No unnecessary words or repetition—ideal for a simple tool.

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 is simple with one parameter and no output schema, so a one-liner might be acceptable. However, the absence of usage context, parameter semantics, and behavioral details leaves room for misinterpretation. For a cache flush operation, one would expect at least a note on what the 'id' references and any immediate effects.

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 description coverage is 0%, so the description must compensate for the undocumented 'id' parameter. Saying 'for a specific site' implies id refers to a site but does not explicitly state 'id: The site ID' or provide format/validation details. This minimal implication adds only slight meaning beyond the schema's bare property name.

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 action ('Flush'), the resource ('object cache'), and the scope ('for a specific site'). It distinguishes itself from sibling cache-related tools like pressable_purge_edge_cache by specifying 'object cache' rather than edge cache.

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 is provided on when to use this tool versus alternatives such as purge_edge_cache or toggle_edge_cache. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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