rosh_compile

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

No annotations exist, so the description must bear full burden. It discloses compilation to HTML and no API key, but lacks details on side effects, auth requirements, error conditions, or output structure. Minimal behavioral context.

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 four well-structured parts: purpose, a notable detail (no API key), an illustrative example, and clear parameter definitions. No unnecessary 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?

The description adequately covers the tool's function and parameters, but omits details about the output (e.g., returned format, behavior on errors). Given an output schema exists, the burden is partially relieved, but the description could still be more complete.

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?

With 0% schema description coverage, the description adds significant meaning by naming both parameters and providing allowed values for 'target'. However, 'code' parameter lacks format or constraints beyond 'Rosh source code'.

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 tool compiles Rosh code into a runnable HTML page, a specific verb and resource. It differentiates from sibling tools which manage programs (delete, get, publish, etc.) rather than compile code.

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 'No API key needed' but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives. Usage is implied by the tool's purpose but not contrasted with siblings.

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