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 by structured data. The description does add something beyond that: it discloses a failure mode — it will not synthesize an answer when the corpus lacks coverage. However, it never says whether that manifests as an empty result, an error, or a partial list.

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 short sentences with no waste, and the core capability is stated first. The second sentence is a little elliptical but still earns its place as a behavioral caveat.

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, the description should say what comes back — a list of citations? titles plus snippets? — and it does not. Combined with absent sibling differentiation and an undocumented parameter, an agent has to guess at both selection and return shape.

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 the single `topic` property; the only hint is the phrase "for a topic". The description adds no meaning about what constitutes a valid topic, how broad or narrow it should be, or how the 2000-character limit is meaningfully used.

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?

"Retrieve cited reading evidence for a topic" gives a verb and a resource, but "reading evidence" is undefined and nothing distinguishes this from the sibling tools `search` and `fetch`, which plausibly also retrieve things by topic. An agent cannot tell from this sentence alone which of the three to pick.

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 and no mention of the alternatives `search` and `fetch`, despite them being obvious competitors for a topic-based retrieval call. The second sentence describes a behavior (non-fabrication), not a usage condition or exclusion.

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