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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: page size bounds of 1–24 and a hard availability constraint (conifer/palm/fern unavailable), plus the division of labor between ngPlant authoring and Blender packaging.

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?

Three tight sentences with the resource and page bound front-loaded, and no filler. The ngPlant/Blender sentence is the least essential but still adds authoring context.

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?

An output schema exists, so return format need not be described, and annotations carry the safety profile. What remains under-covered is how to actually drive the search — the query and offset parameters get no treatment anywhere, which matters for a three-parameter discovery tool.

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% and none of the three parameters (limit, query, offset) are documented in the schema. The description only gestures at pagination ('pages of 1–24'), leaving the meaning and syntax of query and offset unexplained, so it fails to compensate for the coverage gap.

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?

States a specific verb (discover) and resource (ngPlant vegetation templates) and distinguishes itself from the vegetation_create/edit/inspect siblings as a browsing tool. The phrase 'bounded controls' is vague, but the core purpose is 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?

The description explains which template categories are usable for the current production image and which are unavailable, which implies the useful scope of a search. However, it never states when to reach for this tool versus vegetation_create, vegetation_inspect, or assets_search, so the routing guidance is only implied.

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