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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description's only added behavioral content is the default field set, which is really parameter information; it says nothing about matching semantics (exact/prefix/substring), result ordering, or how limit interacts with paging. Adequate but thin for a search tool.

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?

Two short sentences, purpose front-loaded, no filler or redundancy in phrasing. It is efficient, though the second sentence spends its budget restating schema defaults rather than adding new information.

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 fully documented parameters, complete read-only annotations, and no output schema to explain, the definition is close to self-sufficient for invocation. The residual gap is search behavior (match type, ordering, multi-language handling), which an agent would have to discover empirically.

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%, including the fields enum, limit bounds, and language example, so the baseline is 3. The description's default-fields sentence duplicates what the schema already states verbatim, adding no new meaning about how query matching or language fallback works.

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 and resource: "Search for concepts in a SKOS vocabulary." An agent can tell it apart from the get-style siblings (skos_get_concept, skos_get_vocabulary) by inference, but the description never names those alternatives explicitly, so sibling differentiation is left implicit.

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 second sentence describes default search behavior rather than when to choose this tool over skos_get_concept or skos_get_vocabulary. There is no stated context, prerequisite, or exclusion (e.g., "use this when you only have a label fragment; use skos_get_concept when you already have a URI").

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