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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description correctly reinforces that this is a reference/browse operation but adds no extra behavioral context such as result volume, ordering, or coverage limits, so a 3 is appropriate.

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 short sentences with no filler, front-loading the tool's identity before the contextual explanation. It is slightly padded by the second sentence restating what NTEE codes are, which a taxonomy-savvy agent may not need.

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 values need not be described, and the 0-required-parameter design means the tool can be called with no arguments. The one real gap is that the description omits how the two optional parameters select different browse modes, but coverage is otherwise adequate.

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 100%, and the schema itself gives concrete examples for both `query` ("K31", "K6A", "education") and `category` ("A" for Arts, etc.). The description supplies no additional parameter meaning, so the baseline 3 applies.

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 pairs a specific verb ("Browse") with a specific resource (NTEE classification codes) and expands the acronym, explaining these codes classify nonprofits by primary purpose. No sibling tool touches taxonomy lookup, so an agent can distinguish it immediately from search_funders, get_funder_profile, etc.

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?

It states the downstream purpose ("find the right NTEE code for searching or understanding a foundation's focus area"), which implies when an agent should reach for it. However, it never explains the two distinct modes the schema exposes (lookup by code vs. free-text search vs. category browse), nor does it name any alternative tool or condition.

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