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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable behavioral context: 'No LLM call' (performance hint), the comparability constraint across concept_type/embedding_model slices, and the specific semantics of 'review' view. These go beyond what annotations state, so a 4 is warranted.

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 five sentences, front-loaded with the core purpose and key constraints. It avoids fluff and includes a useful doc link. It is appropriately concise for the complexity, though it could be slightly more structured by separating the review-view note, but overall it's efficient.

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 listing tool with an output schema, the description covers the essential decisions: the two views, the alternative for detail, the comparability caveat, and the read-only nature. It does not explicitly mention pagination behavior, but the schema provides limits/offsets and the output schema covers return structure. The review-view distinction is important and well stated. Overall, nothing critical is missing.

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 63%, so the description should compensate for undocumented parameters (limit, offset, sort_order). It does hint at filtering via 'usage counts' and 'type/model facets', which maps to min_ref_count and concept_types, but it does not clarify pagination or sort semantics. Since the schema already documents the key params (view, search, concept_types, min_ref_count, sort_by), the description adds only marginal value, so a 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 states a specific verb ('Browse') and resource ('organization concepts') and enumerates the key facets returned (aliases, usage counts, type/model). It explicitly differentiates from the sibling get_semantic_concept by directing users there for details and neighbors, so an agent can immediately tell this is the list operation.

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 clearly names the alternative tool (get_semantic_concept) and the condition that selects it (when details/neighbors are needed). It also explains the two view modes, including the special 'review' behavior, which helps the agent choose the right view. The pointer to documentation adds further context for when this tool is appropriate for vocabulary review.

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