read_publication

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

No annotations are provided, so the description carries the full burden. It implies a read-only single fetch, but says nothing about permissions, error behavior when the publication is missing, or what is returned. For a bare read tool this is thin but not misleading.

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, which is structurally good. The brevity tips into under-specification given the 0% parameter coverage, but the sentence itself earns its place.

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?

Two required parameters with no schema descriptions, no annotations, and no output schema, so the description is the only source of meaning — and it omits the identifier format, the return shape, and the distinction from search_library/read_rule. Inadequate for the tool's actual complexity.

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% for both required parameters, and the description does not compensate. It never explains what 'publication' should be (ID, DOI, title, slug) or what form 'episode_id' takes, so the agent must guess at both required inputs.

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 ('Read'), resource ('publication'), and scope ('from the episode's library'), so the agent knows it fetches a single item. It does not distinguish itself from the sibling read_rule (same pattern, different resource) or from search_library, which likely returns multiple publications.

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?

No guidance on when to use this versus search_library (to find a publication) or read_rule (to read a rule). The 'one publication' phrasing implies a single-item lookup, but no alternatives or exclusions are named.

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