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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds value by specifying the output structure (concept hierarchy with action links) but does not disclose potential limits, pagination, or ordering. It adds moderate context beyond the annotations.

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 sentences with no redundant wording. The core purpose and scoping are front-loaded, followed by the return format. Every word contributes to the tool's understanding.

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?

For a simple read-only browse tool with one optional parameter and no output schema, the description provides sufficient information for an agent to know what to expect. It names the return structure and the scoping mechanism. Minor omissions like pagination or result limits are not critical for a taxonomy browse, so the description is nearly complete.

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% (the sole parameter has a description: 'Optional dimension slug to scope to'). The description echoes this scoping concept but adds no new parameter-specific details, such as how to obtain a valid slug or constraints on the slug format. Since coverage is high, baseline 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 clearly states the verb 'browse', the resource 'master ontology taxonomy tree', and the optional dimension scoping. It also describes the return value as a concept hierarchy with action links, distinguishing it from siblings like search_ontology and resolve_ontology_concept, which have different verbs and purposes.

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 guidance on when to use this tool versus alternatives. The description mentions optional scoping but does not explain when to browse versus search or resolve concepts, nor does it reference sibling tools. An agent would have to infer usage context from the name and description alone.

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