assets-prefab-open

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

Discloses that modifications apply to all instances, which is key, but does not mention side effects like locking, unsaved changes, or performance impact. No annotations provided, so description carries full burden.

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?

Two sentences plus a note, each adding value: action, effect on instances, and exit instruction. No wasted words.

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?

Explains purpose and effect, but lacks details on return value (no output schema) and prerequisites (e.g., prefab must exist in scene). Could mention error conditions.

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?

Input schema covers the parameter well (100% coverage) with description of how to reference it. The tool description adds no extra parameter semantics beyond what's in the schema.

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 clearly states verb 'Open' and resource 'prefab edit mode for a specific GameObject', differentiating it from sibling tools like 'assets-prefab-close'.

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?

Explicitly says when to use (to modify prefabs) and provides a note to use 'assets-prefab-close' later, but does not explicitly state when not to use or list alternatives.

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