statusbar.report

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

No annotations are provided, and the description only states that the tool reports information. It does not indicate whether the tool is read-only, has side effects, requires permissions, or any other behavioral traits. The agent is left to assume it is a safe read operation, but this is not confirmed.

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 sentence with no unnecessary words. It is appropriately concise and front-loaded.

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 no parameters and no output schema, the description is minimal. It provides the essential purpose but lacks details about the format or content of the returned statistics. For a simple report tool, this may be adequate, but it could be more complete.

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 input schema has no parameters, so the description does not need to add meaning beyond that. With 100% schema description coverage, a baseline of 4 is appropriate. The description simply confirms that no parameters are needed.

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 reports status bar context and scene statistics, with a specific verb and resource. It distinguishes from sibling report tools like uv.report or volume.report by focusing on the status bar. However, it is somewhat vague about what exactly 'context and scene statistics' entails.

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. Given the abundance of sibling report tools, the agent would benefit from knowing when to choose statusbar.report over others, but no such information is given.

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