Get Metadata Cache Status

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

The description explicitly states the tool does not expose cached content, which is a behavioral constraint. However, with no annotations provided, the description carries the full burden and does not disclose other behaviors such as required permissions, rate limits, or whether the tool is safe (read-only hints).

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 sentence that is concise and front-loaded with the core purpose. While it could benefit from additional context, every word serves a purpose and there is no extraneous content.

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 one undocumented parameter and no output schema, the description is incomplete. The agent lacks information about the output format or structure of the cache settings and counters, and the 'profile' parameter is unexplained, which is inadequate for proper tool invocation.

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 input schema has one parameter 'profile' with no description (0% schema coverage). The tool description does not explain what 'profile' represents or how to use it, leaving the agent without necessary semantic context to use the parameter correctly.

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 tool returns profile-scoped metadata cache settings and counters, with a specific constraint of not exposing cached content. This distinguishes it from sibling tools like ob_refresh_metadata_cache which handles cache refresh operations.

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. There is no mention of appropriate contexts, prerequisites, or when to avoid using it, leaving the agent to infer usage from the name alone.

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