app-info

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

The description implies a read-only operation by using the verb 'Report', but it does not explicitly state that the tool has no side effects or that it is safe to invoke. Without an annotation like readOnlyHint, the description carries the entire burden of transparency, and it only partially fulfills this by hinting at non-destructive behavior.

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, concise sentence that lists the exact items to be reported. It avoids any redundant words or unnecessary details, achieving high clarity with minimal text.

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?

While the description lists the specific fields reported, it does not mention the output format, how the information is structured, or any additional context such as whether the report is human-readable or machine-parseable. It also lacks examples or notes on when this tool is most useful, leaving some ambiguity about its practical application.

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 description coverage is 100% trivially. There is nothing for the description to add beyond what the empty schema already conveys, making this dimension fully satisfied.

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's function: reporting specific Blender application state items (runtime, active file, dirty state, scene, workspace, render engine). It uses a specific verb 'Report' and enumerates the exact fields, leaving no ambiguity about what information is provided.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives, any prerequisites, or typical scenarios. It lacks any indication of how to interpret the report or what actions might follow.

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