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

With no annotations, the description carries the behavioral disclosure burden. It does convey that this is a public read-style fetch from a catalog, which is useful, but it does not disclose behavior for unknown slugs, error conditions, or the shape of the returned 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?

One sentence with no filler, and the essential identifying constraint ('by slug') is front-loaded. Every word contributes to tool selection and invocation.

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 simple single-parameter public fetch, the description is nearly sufficient: it identifies the tool, source, and lookup key. The only missing piece is what happens when the slug does not exist, but that is a minor gap for an otherwise straightforward retrieval tool.

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?

The input schema already fully documents the single 'slug' parameter with an example. The description's 'by slug' wording merely repeats the schema's meaning without adding format, constraints, or lookup semantics beyond what is already provided.

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 states a specific verb ('Fetch'), a specific resource ('one aicoolies tool'), and a precise lookup key ('by slug'). This clearly differentiates the operation from the sibling tools that list, search, or fetch catalog context/meta.

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 implies this is for retrieving a single known tool by slug, which contrasts with listing or searching tools. However, it does not explicitly state when to prefer this over siblings, such as 'use search_tools when you don't know the slug'.

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