get_authorAuthor profile + their audiobook works. Returns biography, photo, country, and the full list of audiobook editions where this person is credited as author / co-author / editor.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Author slug (lowercase, hyphenated). Discoverable via search_audiobooks results. Example: "stephen-king". |
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds return content details but no additional behavioral traits beyond what annotations imply. No contradiction.
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 sentences, front-loaded with purpose, no wasted words. Every sentence adds value.
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?
Output schema exists, so return values are covered. Description lists key return elements. For a simple, single-parameter, safe tool, this is fully adequate.
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 100% for the single parameter 'slug'. Description does not add new parameter info beyond the schema's own description, so baseline 3 applies.
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 clearly states verb 'get' and resource 'author profile', lists specific returned fields (biography, photo, country, editions). Differentiates from siblings like get_narrator by specifying author/co-author/editor role.
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?
Implies when to use (when slug from search_audiobooks is available). Does not explicitly state when not to use, but the context is clear from the description and sibling differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but `compare_all_offers` and `find_cheapest_offer` overlap in pricing queries. Descriptions clarify the difference (full table vs. cheapest only), so ambiguity is low. Similarly, `search_audiobooks` and `search_by_filters` are distinct in input style.
All tools follow a consistent verb_noun pattern in snake_case (e.g., `browse_genres`, `get_audiobook`, `search_by_filters`). No mixing of conventions or irregular naming.
13 tools cover browsing, searching, detailed info, price comparison, analytics, and profiles. The number is well-balanced for the catalog's scope—neither sparse nor excessive.
The tool set covers key workflows: discovery, search, details, price comparison, trends, rankings, and partner info. Minor gaps like user reviews or advanced filtering (e.g., partner filter in V2) are acceptable for a focused catalog.