Execute a snippet on a host

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description need not restate the mutation profile. But it adds no behavioral context beyond the title: no mention of side effects, arbitrary code execution, return behavior, or required host connectivity.

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 short but redundant: both sentences say essentially the same thing already captured by the title. No additional information is front-loaded because no information is added at all.

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?

For a tool that executes code on a host, the description is notably incomplete: it does not explain what happens when executed, what the output is, whether this runs arbitrary snippet content, or what hostId and snippetId refer to. The absence of an output schema makes the missing return-value description especially costly.

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 description coverage is only 33%, so the description should compensate for undocumented hostId and snippetId, but it does not mention any parameters. The only parameter with semantic help is inputValues, and that help comes from the schema, not the description.

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 a specific verb and resource: executing a snippet on a host. However, it merely repeats the title and does not differentiate itself from sibling snippet tools or other execution tools.

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 is given about when to use this tool versus alternatives such as termix_snippets_get_specific_snippet, termix_snippets_create_new_snippet, or fleets run-command tools. The usage context is only implied by the verb 'execute'.

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