marrow_install_template

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

No annotations are provided, so the description carries full responsibility. It only states that the template becomes an active workflow, but does not disclose side effects (e.g., whether it overwrites existing workflows), permission requirements, or reversibility. This is a significant gap for a mutation 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?

The description is two short, front-loaded sentences with no redundancy. The action is stated first, followed by a direct usage instruction, making it easy to parse.

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 covers the essential purpose and usage, but lacks detail on expected outcomes or side effects. Since there is no output schema and no annotations, the agent may be left unsure about the return value or whether installation is additive or replacing.

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% with a clear description for 'slug'. The description adds valuable context by instructing the agent to pick the slug from marrow_list_templates, tying the parameter to a specific source and meaning beyond the schema's generic 'Template slug to install'.

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 action ('Install a workflow template into your fleet as an active workflow') with a specific verb, resource, and destination. It distinguishes from siblings like marrow_list_templates, which lists templates, making the install action unambiguous.

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?

Provides explicit contextual guidance: 'Use after marrow_list_templates to pick one.' This tells the agent when to use the tool, but does not mention alternative tools or when not to use it, so it falls short of a 5.

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