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 fully covered. The description adds only the scoping fact that it is limited to the account's Forest and the useful domain note that slugs are the prefix of concept IDs; it says nothing about pagination, result volume, or ordering beyond what the output schema presumably encodes.

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?

One sentence, no filler, with the scope (account's Forest) stated before the field list. The embedded slug explanation earns its parenthetical because it links this tool's output to concept-ID usage elsewhere.

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 present and annotations covering behavior, the description only needs to convey scope and purpose, which it does. What is missing is any routing hint telling the agent when to reach for this over the other list_* tools.

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, which is the baseline-4 case; there is nothing about inputs to get wrong. The parenthetical explaining that a slug is what concept IDs start with adds interpretive value for how the returned values are used downstream.

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?

It names the resource (the trees in the account's Forest) and enumerates the fields returned (slug, name, description, source), so an agent knows what this call yields. It stops short of distinguishing itself from siblings such as list_directory, list_types, or get_inventory, which all sound like enumeration calls.

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 description gives no when-to-use signal, no prerequisites, and never names an alternative among the seven siblings. An agent must infer from the resource name alone that this is the way to discover tree slugs before using concept-ID-based tools.

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