Create Post-Install Script

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

No annotations are provided, so the description must disclose behavioral traits. It mentions constraints (plain text, 10 MB limit, 30-minute timeout) but does not describe side effects, idempotency, naming conflicts, or return values, leaving gaps for a creation tool.

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 concise sentences front-loaded with the main purpose, followed by key constraints. No wasted words; every 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?

The description is fairly complete for a simple creation tool with 3 parameters and no output schema. It covers constraints on content but lacks details on what the tool returns, permissions needed, or how the script is used post-creation. Still, it provides adequate context for an agent to invoke it 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?

Schema coverage is 100%, so the schema already documents all 3 parameters. The description adds value by specifying that content must be plain text (already in schema) and adding size (10 MB) and timeout (30 min) constraints not present in the schema, clarifying proper usage.

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 'Create a new post-install script', which is a specific verb and resource. It distinguishes from sibling tools like delete, list, update by implying creation. The constraints (plain text, size, timeout) further clarify the scope.

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 does not explicitly state when to use this tool versus alternatives. While the name and sibling list imply it's for creation, no guidance is given on prerequisites, when not to use it, or how it compares to update_post_install_script.

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