metadata_objects_catalog_cache_clear

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

With no annotations, the description carries the full burden. It clearly identifies what is affected ('cached metadata objects') and the scope ('current session'), which is useful. However, it does not mention consequences such as cache repopulation, performance impact, or whether this only affects in-memory state.

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 clear sentence with no filler. The action, resource, and scope are all front-loaded, and every word earns its place.

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 and has an output schema, but with no annotations and no usage guidance the description leaves some ambiguity about side effects and prerequisites. It is minimally adequate but not fully complete for an agent deciding whether and when to invoke it.

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 schema has 0% description coverage and the description does not explain the 'session_id' parameter at all. The phrase 'current session' loosely connects to it, but the agent is left to guess what values are valid and how the default relates to the current session.

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 'Clear' and the resource 'cached metadata objects', scoped to the current session. This distinguishes it from related catalog/query tools that fetch or read metadata, and the action is unambiguous.

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 given on when to clear the cache, when not to, or which sibling tool might be an alternative. The description only states what the tool does, not the situations that warrant using it.

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