label_show

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

No annotations are provided, and the description only says 'show details,' which implies a read operation. It does not disclose what happens if the label ID is invalid, whether authentication is required, or any other side effects. Minimal behavioral insight beyond the obvious.

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 a single, clear, and front-loaded sentence: 'Show details of a specific label.' No unnecessary words, and it efficiently communicates the purpose.

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?

The tool has no output schema and no annotations. For a simple retrieval tool, the description is adequate but lacks details about the output (what constitutes 'details'), potential errors, or any behavioral notes. It covers the basic purpose but not the full context.

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% for the single parameter 'id' with a description 'Label ID (UUID).' The tool description adds no further meaning to the parameter, so it meets the baseline of 3 (schema does the heavy lifting).

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 states it shows details of a specific label ('Show details of a specific label'). It distinguishes itself from sibling tools like label_list, which lists labels, by focusing on a single label. However, it does not explicitly state the distinction.

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?

No guidance on when to use this tool versus alternatives like label_list or other show tools. There is no mention of prerequisites (e.g., label must exist) or when not to use this tool.

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