get_tool

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

Describes lookup by exact slug and output summary, but does not mention error handling for missing slugs or invalid inputs. Without annotations, this is the main gap.

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?

Well-structured with clear sections (BEHAVIOR, USAGE GUIDELINES, EXAMPLE QUERIES). Front-loaded with purpose and no unnecessary sentences.

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?

Provides good context on output and sibling tools, but lacks details on error cases or response format (no output schema). Adequate for most use cases.

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 covers slug parameter fully. Description adds example values and exact match behavior, but no additional semantics beyond what schema provides.

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 retrieves a full profile for a specific tool by slug, listing returned fields and distinguishing from sibling tools like get_pricing and get_alternatives.

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?

Explicitly provides use cases (e.g., user asking about a tool), when to prefer alternatives, and example queries. Also advises using it to verify slug existence before other calls.

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