get_editions_by_title

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

With no annotations, the description carries the full burden of behavioral disclosure. It does convey two useful behaviors: matching is exact and the result set may contain multiple known editions. It does not disclose potential edge cases such as case sensitivity, empty results, authentication requirements, or whether the response is a list, relying instead on the word 'all' and the sibling names.

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 clean sentence with no filler. It front-loads the purpose and match semantics, and every word contributes to understanding the tool.

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 one-parameter lookup tool with no output schema, the description covers the core semantics adequately: it names the resource, the exact-match condition, and the plural result set. It could be richer by explicitly stating the return format or behavior when no match is found, but those are minor gaps for such a simple 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?

Schema coverage is 100%, and the schema description 'Exact edition title to look up' already captures the only parameter's semantics. The description repeats essentially the same idea, adding no meaning beyond the structured schema, so it meets the baseline but doesn't add value.

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 uses a specific verb and resource: 'Get all known editions of a book by exact title match.' It clearly distinguishes this from the ISBN-based sibling (get_editions_by_isbn) and the single-edition lookups (get_edition_by_id), making the tool's scope immediately obvious.

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 'exact title match' qualifier hints at the appropriate use case, implying the caller must already know the exact title rather than a partial or fuzzy term. However, it does not explicitly contrast with siblings like search or get_editions_by_isbn, leaving the agent to infer when this tool should be preferred over alternatives.

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