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

Annotations already indicate read-only and non-destructive behaviorcompress. The description adds meaningful beyond-structure value by specifying that two URL fields exist ('url' for the TAAFT page, 'website_url' for the external website) and instructing to preserve returned URLs exactly. This is a valuable behavioral disclosure not captured in the schema or annotations.

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?

Two terse sentences with no filler. The first states the core action, the second gives concrete field-level guidance for using the response.

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 single-parameter read-only tool with a 100%-described schema, this is well covered. The instruction to preserve URLs and distinguish the two URL fields partially compensates for the missing output schema, though it doesn't enumerate other response fields or 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?

The input schema already fully documents the sole parameter 'slug' with the note that it is returned by search_tools, so schema coverage is 100%. The description adds no additional semantic meaning beyond repeating 'by slug'. Baseline of 3 applies since the schema carries the descriptive load.

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?

Description states a specific verb ('Get'), a specific resource ('one TAAFT AI tool'), and the key identifier ('by slug'). The singular phrasing clearly differentiates it from the sibling search_tools, and the mention of 'public details' sets expectations for the response.

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 tool's details by slug, with the schema noting the slug comes from search_toolsörgcu. It clearly establishes context as the follow-up to a search but does not explicitly say 'use search_tools to find the slug first' or exclude other use cases. No explicit exclusions, but the context is clear enough.

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