script_manage

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

No annotations are provided, so the description carries full burden. It only notes that 'detach' is undoable, but fails to disclose side effects, permissions, error conditions, or return value structure (despite having an output schema).

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 concise, using bullet points for operations. It is front-loaded with the main purpose. However, the header line could be more polished, and each sentence earns its place.

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 has three operations and an output schema (not shown), the description does not explain what each operation returns or error behavior. It lacks prerequisites like script existence or session context. It is minimally complete for a simple script management tool.

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 coverage is 0% according to context signals. The description adds meaning for the 'op' parameter by listing its enum values, but the 'params' and 'session_id' parameters remain undocumented. The description does not specify what keys 'params' should contain for each operation.

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 that the tool handles script reading, detachment, and outline, listing three distinct operations with brief explanations. It distinguishes from sibling tools like script_attach and script_create by focusing on operations not offered elsewhere.

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 mentions a 'resource form' preference for active-session reads but does not explicitly guide when to use this tool versus alternatives like script_patch or script_attach. No exclusions or when-not-to-use guidance is provided.

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