search_labels

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

States it returns label on exact match, but behavior on no match is unspecified. Also does not clarify case-sensitivity or trimming. Annotations indicate read-only, consistent.

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 succinct sentences, no extraneous information, front-loaded with key constraint.

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?

Adequate for a simple lookup tool with one parameter and read-only nature. No output schema but return expectation is clear.

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 0%, but description adds that the 'name' parameter refers to the label's exact name. Provides some context beyond schema but still minimal.

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?

Clearly states it searches labels by exact name and returns the label. Differentiates from siblings like list_labels (lists all) and get_label (likely by ID).

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?

Explicitly mentions exact match, not partial, guiding correct usage. Lacks explicit mention of when to use alternatives or what to do if name unknown.

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