label-byPublicId

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

No annotations are provided, so the description carries full burden. It states 'Retrieves' implying a read-only operation, but does not disclose behaviors such as error conditions (e.g., missing label), permissions required, or whether it returns only selected fields. Minimal disclosure beyond the name.

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 extremely concise at 10 words plus a tag. It is front-loaded with the key action. However, it could include more helpful details (e.g., output format) without becoming verbose.

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 retrieval tool with one parameter and no output schema, the description is minimally adequate. It lacks details about return values or edge cases, and given the context of many sibling tools, a brief hint about expected output or common usage would improve completeness.

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 0%. The description does not explain the parameter 'labelPublicId' (e.g., what constitutes a public ID, how to obtain it). The schema defines a string with minLength=12, but the description adds no semantic value beyond that.

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 'Retrieves a label by its public ID', using a specific verb (Retrieves) and resource (label by public ID). It distinguishes from sibling label tools like create, delete, and update, which modify resources.

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 for retrieving a label by ID, but provides no explicit guidance on when to use this versus alternative tools (e.g., label-byId might be a sibling? Actually not listed, but other lookup tools exist). No mention of prerequisites or exclusions.

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