hyperframes_add_block

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

The description fails to disclose key behavioral details. It implies a write operation ('Install') but does not explain side effects (e.g., whether blocks can be overwritten, if internet access is needed, or how 'no_clipboard' affects behavior). With no annotations, the description carries full burden but only covers basic purpose.

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, with a single sentence stating purpose followed by a structured, bullet-like argument list. Every word serves a purpose, and the information is front-loaded. No unnecessary elaboration.

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?

The description is incomplete given the tool's complexity. It does not explain the return value (despite an output schema existing), side effects, or the behavior of the omitted 'no_clipboard' parameter. An agent would need additional context to use the tool correctly.

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 description adds meaning for the two required parameters beyond the schema's bare type: 'project_path' is specified as an absolute path, and 'block_name' includes an example. However, the optional 'no_clipboard' parameter is completely omitted from the description, reducing completeness given the low schema coverage (0%).

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 purpose with a specific verb ('Install') and resource ('a block from the Hyperframes catalog'). It distinguishes this tool from sibling tools like hyperframes_catalog (likely for browsing) and hyperframes_init (project setup), as it specifically focuses on adding a block to an existing project.

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?

The description provides no usage guidance. It does not indicate when this tool should be used over alternatives (e.g., after browsing with hyperframes_catalog, or before using hyperframes_render). No prerequisites or subsequent steps are mentioned, leaving the agent without context on proper workflow.

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