lookup_wlo_vocabulary

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

No annotations are provided, so the description carries the transparency burden. It implies a read-only, safe operation by saying 'look up' and 'discover', and it mentions that the output includes 'valid labels and URIs'. However, it does not disclose response format, pagination, or any potential errors, leaving some gaps.

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 three sentences with no redundancy. It front-loads the purpose, then expands on the specific vocabularies, and closes with usage context. Every sentence contributes value.

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 simple single-parameter lookup tool with no output schema, the description provides sufficient context: what it returns (labels and URIs), the known vocabularies, and when to use it. It could be more complete by describing the return structure or adding an example, but it is not necessary given the tool's simplicity.

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?

The schema has 100% coverage with a single parameter 'vocabulary' that includes an enum and a detailed description for each value. The description reinforces the same information by listing the German terms, but it does not add meaning beyond the schema's own documentation, so 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 uses a specific verb 'look up' and names the resource 'available values for WLO filter parameters'. It further lists the exact vocabularies, making the tool's function unambiguous and distinct from the sibling search and retrieval tools.

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 states 'Useful before calling search tools to find the correct filter values', clearly indicating when this tool should be used. It does not explicitly name alternatives or when not to use it, but the context of pre-search lookup is sufficiently clear.

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