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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds value only by disclosing the shape of the payload (broader/narrower/related), which matters because there is no output schema; it says nothing about missing-URI behavior or label-language fallback.

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?

A single sentence that front-loads the action and resource, then lists the returned relations. No filler, no restatement of the title, nothing that fails to earn its place.

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 no output schema present, the description usefully summarizes the returned concept relations, and the annotations cover the safety profile. For a two-parameter read tool this is nearly complete; only the language-fallback behavior and error case for an unknown URI are unaddressed.

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%, so both 'uri' (with an example) and 'language' (with examples) are already documented in the schema. The description contributes nothing extra about parameter semantics, 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 names a specific verb and resource ('Get details of a single SKOS concept by its URI') and enumerates what the result includes (broader, narrower, related). It is clearly distinguishable from skos_search (search) and skos_get_vocabulary (whole vocabulary) by the words 'single' and 'by its URI', though it never names those siblings explicitly.

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 explicit when-to-use guidance and no mention of the sibling alternatives (skos_search, skos_get_vocabulary). The phrase 'by its URI' weakly implies the caller must already hold a concept URI, but the choice between this tool and skos_search or skos_get_vocabulary is left entirely to inference.

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