rhino_block_manager

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

No annotations are provided, so the description must carry behavioral disclosure, but it only states the dialog opens. It does not mention modal blocking, possible document changes after user edits, whether it is a UI-only action, or any return value; output schema aside, these traits are undisclosed.

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?

A single five-word sentence with no filler. The action and object are front-loaded, making it very concise.

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?

For a 0-parameter tool the description is short, but that brevity hides significant gaps: no indication of when to use it over block list/define/insert, no behavioral detail about the dialog, and no mention of effects on the document. With no annotations, the agent cannot judge side effects or workflow fit.

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 zero parameters and an empty schema, so there is nothing for the description to add. Baseline 4 applies because parameter semantics are trivially complete.

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 specific verb 'Open' with a clear resource 'Block Manager dialog', so the agent knows it opens a UI dialog rather than performing a block operation. It does not explicitly differentiate from block-related siblings, but the dialog focus makes it identifiable.

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 given about when to use this tool versus block list, define, insert, or explode siblings. The description only states the action, leaving the agent to infer that a UI dialog is the intended path for interactive block management.

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