Show tag

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

Annotations already provide strong safety signals (readOnlyHint, idempotentHint, destructiveHint=false). The description adds the HTTP GET method, which is consistent with these hints but does not disclose additional behavioral details such as error handling, return format, or edge cases. With annotations present, the description adds modest value beyond them.

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, using three short sentences to convey the action, resource, and endpoint. It is front-loaded with the purpose and contains no redundant or filler information.

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-tag retrieval with one well-documented parameter and rich annotations, the description is adequate. It does not explicitly state the return value (the tag object), but this is easily inferred from the tool name and GET endpoint, and there is no output schema that would require explanation.

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 has 100% coverage of the parameter 'id' with the description 'The ID of the tag to retrieve.' The tool description does not add any further meaning beyond the schema, so it stays at the baseline of 3.

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 the specific verb 'retrieves' with the resource 'tag' and explicitly states the API endpoint (GET /v2/tags/{id}). This clearly distinguishes it from siblings like listTags, createTag, and deleteTag, making the tool's purpose unambiguous.

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 fetching a specific tag by ID, but it does not explicitly mention alternatives or when not to use it. For example, it doesn't note that listTags should be used for listing all tags, so the guidance is limited to what can be inferred from the tool name and description.

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