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

With no annotations, the description carries the full burden and does exceptionally well. It discloses that it plainly reports error pages or access walls instead of inventing references, that a nextStep field is returned with browser actions, and even includes measured performance stats on 20 mixed sources. This goes far beyond typical descriptions.

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?

The description is front-loaded with the core function, then usage, then behavior and performance. It is longer than average but every sentence contributes useful information. The measurement sentence is unusual but justifies reliability. No redundancy or filler.

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?

Given there is no output schema, the description sufficiently explains what the tool returns (structured record, RIS, BibTeX) and handles failure modes (nextStep field). It also gives a concrete sense of expected success rates. For a single-parameter read tool, this is complete.

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?

The input schema already describes the single parameter 'url' as 'Address of the page to read', giving 100% coverage. The description adds only that the page declares citation details about itself, but doesn't add syntax or format nuance. Baseline 3 is appropriate since the schema does the heavy lifting.

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 reads citation details a web page declares about itself and returns them as a structured record plus RIS and BibTeX. It also lists supported source types, which adds specificity. However, it does not explicitly distinguish itself from the sibling tool 'extract_citations', so it misses full sibling differentiation.

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 description provides explicit usage context: 'Use when a source has to be cited, archived, or added to a reference manager.' It doesn't mention when not to use it or name alternatives, but the guidance is clear enough for typical selection.

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