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

The description adds useful behavioral context beyond the annotations: it notes that versions are immutable, mentions 'pinned JSON/CSV links,' and explicitly instructs the agent to follow next_offset for pagination. This supplements the readOnly/idempotent hints without contradicting them.

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 two short sentences with no fluff. The primary purpose is front-loaded, and the pagination instruction is placed second, making the key information immediately visible.

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 read-only annotations and an output schema present, the description only needs to fill key usage gaps, and it provides pagination behavior and result content. However, it omits parameter guidance and any roadmap for choosing among sibling tools, leaving the overall guidance adequate but not comprehensive.

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%, so the description must compensate, but it only hints at pagination via 'Follow next_offset.' It does not explain symbol, limit, or offset semantics directly, nor does it describe how these parameters shape the returned revisions.

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 uses a clear verb, 'Browse,' with an explicit resource: immutable published versions, reasons, and pinned JSON/CSV links. It clearly identifies the tool's read-only purpose, but it doesn't name or explicitly differentiate itself from siblings like compare_company_revisions.

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 only guidance is 'Follow next_offset,' which is a pagination instruction rather than context for when to choose this tool over alternatives. No mention is made of compare_company_revisions, get_company_file, or other siblings, so an agent gets no help deciding which tool fits the task.

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