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

With no annotations, the description must fully convey behavioral traits. It states the tool retrieves full details but does not mention any side effects, authentication needs, or limitations. The description is straightforward but lacks depth on expected behavior or return characteristics.

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 a single sentence of 13 words, immediately stating the purpose and key detail (slug origin). No unnecessary words; every phrase earns its place.

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 get-by-identifier tool with one parameter and no output schema, the description is complete. It specifies the input (slug), how to obtain it (from search_ai_tools), and the output (full details). The sibling tools are listed, providing additional context.

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 schema covers 100% of the parameter with description 'Tool slug, e.g. 'notion-ai'.' The description adds value by connecting the slug to 'search_ai_tools', providing operational context. This extra information helps the agent understand the parameter's origin, making semantics clearer than schema alone.

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 verb 'Get' and the resource 'full details for one AI tool', specifying identification by slug. It references the sibling tool 'search_ai_tools' to clarify how the slug is obtained, effectively distinguishing itself from the siblings.

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 when to use this tool: after obtaining a slug from 'search_ai_tools'. It provides context on the slug's origin but does not explicitly state when not to use it or give alternative tools for different use cases.

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