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

With no annotations, the description carries the full behavioral burden. It usefully discloses the quota cost ('Counts one install per account') and enumerates the returned artifacts, but says nothing about permissions, whether an existing install is overwritten, or failure modes for an already-installed bot.

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?

A single sentence, front-loaded with the action, then returns, quota, and args. Dense but every clause adds something; no padding.

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?

There is no output schema and no annotations, so the description does the reporting work well with the returns list and quota note. However, for a mutating install operation it omits provenance of the slug, auth/permission needs, and overwrite/error behavior.

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 0%, so the description must compensate. 'Args: slug' merely restates the parameter name; it does not explain what a slug is or where to obtain it (presumably from library_search), leaving the single required argument underspecified.

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?

States a specific verb and resource ('Clone a library bot into this bot') that is clearly distinct from siblings like library_get, library_publish, and library_search. It also says what comes back (recipe steps, tools, prompt, memory_seed), but it never names an alternative sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance; the agent must infer that this is the install counterpart to library_search. The only constraint mentioned ('Counts one install per account') is a quota fact, not routing advice.

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