get_blendfile_summary_datablocks

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

Beyond the readOnlyHint annotation, the description adds no behavioral context. It does not explain what data is returned, whether it operates on the current file, or how the output is structured. The description carries minimal burden and fails to enrich the agent's understanding.

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 extremely short but under-specifies the tool's purpose. It is not concise in a useful way; it is cryptic and poorly structured, likely due to non-native English phrasing. A one-sentence description can be effective, but this one fails to convey meaning.

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 simplicity of the tool (no parameters, read-only), the description is still incomplete. It does not say what the tool returns or how it relates to other scene/summary tools. The agent is left without enough context to select or invoke it correctly.

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 tool has no parameters, so the schema is empty. Baseline for zero parameters is 4; there is nothing for the description to explain about parameter semantics. The description does not need to compensate for any coverage gaps.

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 'Inventaris datablocks file blend' is essentially a broken translation of the tool name, offering no additional clarity. It restates the name without specifying what 'summary datablocks' means or what the tool actually does. It does not distinguish itself from sibling getter tools.

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 context, prerequisites, or alternative tools, making it impossible for an agent to know when this is the right choice.

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