BrinkerAdvisor Reading Guide

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful non-safety context that the response carries source and unknown-date warnings, but says nothing about lookup failure or the shape of the result.

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 compact sentence with the action and scope front-loaded and no redundant padding. The trailing clause about warnings is slightly compressed into near-obscurity, but nothing is wasted.

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, annotation-backed lookup with no output schema, this covers the essentials of what the tool does. It remains thin on caller-relevant behavior: what happens when the ID is not found and what the warnings actually signal.

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 0% and the single parameter carries only a regex pattern with no description. The phrase "exact catalog ID" conveys that an exact identifier is required rather than a fuzzy query, adding modest meaning, but the required format (book- prefix, hex length) is left only to the regex.

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?

States a specific verb (Fetch) and resource (one catalog ID), making it clear this is single-item retrieval. Implicitly distinguishes from search_books (this fetches one exact ID rather than searching) though it never names the sibling explicitly.

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?

"one exact catalog ID" implies the precondition that the caller already holds a precise ID, which differentiates it from search_books. However, no explicit when-to-use, when-not, or named alternative is provided.

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

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description usefully adds that results are bounded and returned in 'existing editorial order,' which is context the annotations do not convey, but it omits pagination/traversal behavior.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized for a two-parameter read tool, though its brevity contributes to the informational gaps elsewhere.

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?

With no output schema and 0% parameter coverage, the description leaves the agent without any sense of the return payload, the meaning of shelf_id values, or how this differs from searching. For a curated-read tool this is under-specified.

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 0% across two parameters, so the description should compensate but largely does not. 'Bounded' loosely gestures at the limit parameter, while shelf_id and its seven enum values are left entirely to the schema with no explanation of what distinguishes the shelves.

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 gives a verb ('Return') and a resource ('publisher shelf') with an ordering qualifier, but the terminology does not match the tool name ('reading path') and the concept of a curated shelf is never explained. It also does nothing to distinguish itself from get_book or search_books.

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?

There is no statement of when to use this tool versus the sibling get_book or search_books, and no prerequisites or conditions are given. The agent must infer usage entirely from the name.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a useful scope constraint (factual metadata only, no commerce/editorial content), but says nothing about result format, result ordering, or how limit/featured_only alter behavior.

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?

A single front-loaded sentence with no filler; the scope constraint is placed where it matters. It is arguably too terse to be maximally useful, but nothing is wasted.

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?

With 6 parameters, zero schema descriptions, and no output schema, the description leaves the agent guessing about query semantics, filter interaction, and result shape. A tool this parameterized needs more than one clause of scope to be callable with confidence.

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 0% across 6 parameters, and the description explains none of them. An agent gets no help understanding whether query matches titles, authors, or both, how query interacts with shelf/category, or what featured_only filters on. The enum values are self-describing but the query semantics are not.

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?

States a specific verb (search) and resource (book metadata) and draws a scope boundary ('bounded factual book metadata; no commerce or editorial prose') that separates it from a generic catalog search. It does not explicitly contrast with get_book or get_reading_path, but the scope statement is enough to identify what this tool returns.

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?

There is no when-to-use guidance, no mention of the sibling tools get_book or get_reading_path, and no indication of when a metadata search is preferable to fetching a single book. The 'no commerce or editorial prose' line is a content boundary, not usage guidance.

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