Read one tag

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds the specific authentication requirement ('key carrying the taxonomy:read scope') and plain-language reassurance ('Nothing is changed'), which go beyond annotations. It does not describe return format, but for a simple read operation this is adequate.

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 brief and front-loaded with the purpose. However, 'Read only' and 'Nothing is changed' are somewhat redundant with each other and the readOnlyHint annotation, adding slight unnecessary repetition. Nonetheless, it remains concise and structured effectively.

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?

This is a simple tool with one parameter, rich annotations, and no output schema. The description covers purpose, safety, and authentication, making it complete enough for correct use. The sibling tool names provide additional context for when to use it, eliminating ambiguity.

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 input schema provides 100% coverage for the single parameter 'id' as 'A UUID'. The description adds no additional meaning beyond the schema, so the baseline score of 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 clearly states 'Read one tag' with a specific verb and resource, distinguishing it from sibling tools like list_tags, create_tag, update_tag, and delete_tag. The 'Read only' phrasing reinforces the read-only nature, making the purpose unmistakable.

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 use for reading a single tag by ID, supported by the schema and sibling context, but it does not explicitly state when to use this tool over alternatives like list_tags. No exclusions or alternative recommendations are provided, only inferred from 'Read one tag'.

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