unfold_block

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

The description adds no behavioral context beyond the annotations. Annotations show it is not readOnly (implies mutation) and not destructive, but the description does not confirm or elaborate. No explanation of side effects, permissions, or reversibility is given.

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 concise (three characters) but at the cost of informativeness. It does not earn its place because it adds no value beyond the tool name. Under-specification undermines conciseness.

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 tool's simplicity (one parameter, no output schema), the description is incomplete. It fails to explain the effect of 'unfolding' a block, such as whether it expands a collapsed block or changes a property. The schema covers the parameter, but the tool's behavior is not fully described.

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 already describes the 'id' parameter comprehensively (100% schema coverage), specifying it is a block, document, notebook, or database ID. The tool description does not add any parameter information, but the baseline of 3 is appropriate since the schema covers the semantic load.

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 '展开块' (unfold block) essentially restates the tool name. It conveys the basic action but does not distinguish from sibling tools like 'fold_block' or specify what 'unfold' means in the context of Siyuan blocks. The verb and resource are clear, but no additional differentiation 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 indicate when to use this tool, when not to, or any prerequisites. It fails to guide the agent on choosing between this tool and alternatives like 'fold_block'.

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