app.info

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

No annotations provided, so description carries full burden. It says 'Report' but does not specify if this is a read-only operation, if it has side effects, or what format the report returns. Lacks clarity on behavior (e.g., does it print to console, return data?). For a tool with no annotations, this is insufficient.

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?

Single concise sentence that front-loads the verb 'Report' and lists items. No wasted words. Every piece of information serves a purpose.

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 0 parameters and no output schema, the description is the sole source of information. It lists what is reported but does not describe return format or structure. For a simple info tool, this may be adequate but lacks completeness about output semantics.

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?

Input schema has 0 parameters, so schema coverage is 100%. Description adds no parameter info because none exist. Baseline for 0 params is 4, and description adds no value beyond schema, meeting baseline.

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?

Description clearly states it reports multiple specific aspects of Blender runtime (active file, dirty state, scene, workspace, render engine). Verb 'Report' combined with resource list makes purpose unambiguous. Lacks differentiation from similar sibling report tools like 'info.report' or 'scene.info'.

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 on when to use this tool versus alternatives. Among siblings, there are many report tools (e.g., 'info.report', 'scene.info', 'tracking.report'), and the description does not help the agent choose. No exclusions or context provided.

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