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

No annotations are provided, so the description must inform about side effects and behavior. It explains the tool uses a live endpoint when credentials are available, otherwise falls back to a bundled snapshot (marked in frontmatter). This is good transparency, though it could mention that the tool is non-destructive and read-only.

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 sentences long, front-loads the core purpose, and adds context without irrelevant details. Every sentence adds value, achieving maximum conciseness.

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's simplicity (one parameter, no output schema, no annotations), the description covers the main aspects: what it generates, how it works (two modes), and where to use the output. It could elaborate on the exact format or limitations, but it is sufficient for an agent to decide and invoke it.

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?

There is only one parameter ('slug') with 100% schema coverage; the schema already provides a clear description and example. The tool description does not add further nuance beyond confirming it identifies a specific bot. Baseline score of 3 is appropriate.

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's function: generating a SKILL.md file for a URBot bot. It specifies the output format (YAML frontmatter, system prompt, capability profile) and intended use (dropping into compatible agents). This distinguishes it from siblings like chat_with_bot or search_bots.

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 explains when to use the tool (to export a bot as an agent skill) and mentions two operational modes (live endpoint vs. snapshot). However, it does not explicitly state when not to use it or list alternatives among sibling tools, which would strengthen guidance.

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