hyperframes_info

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

No annotations provided, so the description must fully disclose behavior. It implies a read-only operation ('Print') but does not explicitly state it is non-destructive, require no authentication, or explain possible errors. Minimal behavioral insight.

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?

One short sentence, front-loaded with the action. No waste, but the brevity sacrifices helpful details. Could be expanded slightly without losing 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?

Tool has an output schema but no description of return values. Given no annotations and vague parameter, the description leaves significant gaps for an agent unfamiliar with Hyperframes.

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?

Schema has zero description coverage for the sole parameter 'project_path'. The description does not explain what a valid project_path is (e.g., file path, URL, ID). No additional meaning beyond the type 'string'.

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 uses specific verb 'Print' and resource 'Hyperframes project metadata', clearly distinguishing it from sibling tools like hyperframes_init or hyperframes_capture. However, 'metadata' is somewhat vague, not specifying what aspects are included.

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 like hyperframes_inspect or hyperframes_info_detailed (if exists). The description does not mention prerequisites or exclusions, leaving the agent without context for selection.

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