get_concept_label

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

No annotations provided, so description carries full burden. States operation is read-only ('Get'), but omits details about returned format, error handling, required permissions, or behavior for missing URIs.

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?

Single sentence, front-loaded with key information, no redundant or superfluous content.

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?

No output schema and rich sibling set (12 tools). Description does not specify return format (e.g., object or array) or handle edge cases (e.g., missing language code), leaving significant gaps for an AI agent.

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% with descriptions for all 3 parameters. Description adds minimal context beyond schema (e.g., 'for a concept URI' aligns with 'uri' param), but does not enrich understanding of 'lang' or 'vocabulary' usage.

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 identifies the verb 'Get' and the resource 'all labels (prefLabel, altLabel, hiddenLabel) for a concept URI'. It distinguishes from siblings like 'get_concept' (gets concept object) and 'resolve_label' (resolves label to concept).

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 description implies usage when needing labels for a concept URI, but does not provide explicit when-to-use/when-not-to-use guidance or differentiate from 12 sibling tools like 'labels' or 'get_concept'.

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