simulation.cache_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a little context by stating 'Risk: read' and noting that authorization/session checks still apply, which is useful, but it does not disclose what data or cache state the status call observes.

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 short and free of obvious filler, but it is more under-specified than appropriately concise. The maturity and policy statements read as boilerplate and do not add tool-specific value.

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?

Although an output schema and rich annotations are present, the description lacks the core purpose and parameter semantics needed to invoke the tool correctly. The agent is left to guess what the status refers to and which optional identifiers select the relevant cache.

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 only 50%, and the description does not compensate. It provides no meaning for `name`, `objectId`, or `_expectedSceneRevision`, which are left undocumented in both the schema and the description. The agent cannot determine which cache is being queried or how the optional parameters affect the result.

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 only restates the command name (`simulation.cache_status`) and labels it as a read. It never says what the tool actually does, such as returning the current status of simulation caches or which cache state is being reported. The purpose is left to inference from the name.

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 about when to use this tool versus alternatives such as `blender_simulation_free_cache` or other simulation tools. The only operational note is that per-request argument checks and session policy apply, which does not help with tool selection.

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