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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so 'Read-only' in the description is redundant with structured data. The one genuine addition is 'Approved facts', which signals curated, authoritative, static content rather than generated answers — a useful contrast with ask_nwb.

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 listing the content, with no padding. The trailing 'Read-only.' fragment restates the annotations rather than earning its place, which keeps it short of a 5.

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 zero-parameter, fully annotated read tool the description is nearly sufficient — an agent knows what it returns and that it is safe to call. What is missing is the boundary against ask_nwb, the closest sibling, which is the one piece of context that would prevent a mis-selection.

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 tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

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 states a specific resource and enumerates its content ('facts about the miracle berry, its three taste effects, the company and its certifications'), which tells the agent exactly what it will get back. It does not, however, distinguish itself from the sibling ask_nwb, which is the tool most likely to be confused with it for informational queries.

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 alternatives. With a sibling named ask_nwb that appears to answer questions about the same subject matter, the absence of any routing rule ('use this for the fixed facts; use ask_nwb for open questions') leaves the agent to guess.

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