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

Annotations already declare the safety profile (read-only, idempotent, non-destructive, closed-world), so the description need not restate that. It does add meaningful behavioral context beyond annotations: the result is an aggregate inventory with counts, status and trust-tier totals, and likely near-duplicate detection, which tells the agent this is a synthesis view rather than a raw listing.

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?

It is a single dense sentence that front-loads the inventory scope and then adds the most decision-relevant details: counts, status, trust tiers, and near-duplicates. There is no wasted or redundant text.

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 an output schema, rich annotations, and 100% parameter schema coverage, most structured information is already available. The description completes the picture of what the inventory contains, but it omits the key routing guidance that would help an agent choose this over sibling tools for specific queries.

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 coverage is 100%, and the `tree` parameter is fully documented in the schema as a slug from list_trees that is optional only when the Forest has one tree. The description adds no parameter guidance beyond that, so the baseline of 3 is appropriate.

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 precisely names the resource and scope: every type, tag, and frontmatter key used by a tree, including aggregates and near-duplicates. It is clearly more than a plain list and is distinguishable from list_types by its counts and cross-key aggregation. The only weakness is that the leading noun phrase omits an explicit verb, though the title supplies 'View'.

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 explicit guidance on when to use this tool instead of siblings like list_types, list_directory, or search_concepts. The description implies an overview/inventory use case but never states when-not-to-use or which alternative to pick for narrower queries.

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