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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by promising 'a short response' (a size/verbosity expectation an agent can plan around) and by disclosing that the payload includes an independence statement and loading state — behavior the agent could not infer from the schema.

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 sentences, front-loaded with the resource and then the enumerated sections, closing with the response-size note. The middle clause is a slight run-on list, but every clause maps to content the agent actually receives.

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?

There is no output schema, so the description carries the burden of explaining return contents — and it does, enumerating all five sections. For a zero-parameter, read-only orientation tool, nothing an agent needs before calling is missing.

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 and fully described, so there is nothing for the description to disambiguate. Baseline of 4 applies.

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 concretely what the tool returns: an overview of the corpus, which collections are loaded, id/page-address conventions, a tool-selection guide, and an independence statement. This clearly separates it from the sibling lookup/search/browse tools, which all operate on specific collections. It stops short of an explicit verb+resource opener, but the enumerated contents make the purpose unambiguous.

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?

Including 'which tool fits which kind of question' strongly implies this is the orientation entry point before diving into the 25+ siblings, but the description never explicitly says 'call this first' nor names when to skip it. Usage is inferable rather than stated.

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