get_blendfile_summary_usage_guess_for_cli

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

The readOnlyHint annotation already establishes that this is a non-mutating read operation. The description adds useful context that it opens the file in background Blender, which suggests headless execution. It does not describe output behavior, failure modes, or assumptions about the Blender installation, but no contradiction exists.

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 efficient sentence with no filler. It front-loads the action and immediately explains the mechanism, making it easy for an agent to parse quickly.

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: one required parameter, a readOnly annotation, and an output schema that can document return values. The description covers the core operation and adds the background Blender detail. It is slightly incomplete in not explicitly routing the agent to the non-CLI sibling, but overall it is adequate for a low-complexity, read-only tool.

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 carry the parameter meaning. The description does indicate that *blend_file* is the file to be opened by Blender, but it does not clarify whether it should be a local path, a relative path, or a CLI-style argument. It adds some semantics beyond the schema, but not enough to fully compensate for the missing schema description.

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 uses a clear verb ('Guess') and a specific resource ('*blend_file*'), and adds an operational detail that it runs in background Blender. However, it does not explicitly distinguish itself from the sibling get_blendfile_summary_usage_guess, so the differentiation relies on the '_for_cli' name and 'background Blender' phrase.

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?

The phrase 'in background Blender' implies this is the command-line/headless variant, which gives some usage context. But it never states when to prefer this tool over get_blendfile_summary_usage_guess or another sibling, so the guidance remains implicit rather than explicit.

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