get-tag

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 a read operation (retrieve) and mentions the return of bookmark counts, but does not disclose potential behavioral traits like authentication requirements, rate limits, or side effects. For a simple retrieval, this is adequate but not exemplary.

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 sentence of 12 words, front-loaded with the key action. Every word serves a purpose without redundancy. It is highly concise.

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?

No output schema exists, so the description should explain return values. It mentions 'including its bookmark counts', which partially describes the return, but it does not specify other typical tag fields (e.g., name, id). However, given the tool's simplicity, it is largely complete and sufficient for an agent to understand what to expect.

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 100% for the single parameter 'tagId'. The tool description adds no extra meaning to the parameter beyond the schema's description; it only refers to the return value. Per the rubric, a baseline 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 the verb 'Retrieve' and the resource 'a single tag by id', explicitly distinguishing from sibling tools like 'get-tags' (plural) and 'get-tag-bookmarks' (which returns bookmarks). It also specifies the inclusion of bookmark counts, which differentiates this from a simple tag retrieval.

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 when a single tag by ID is needed with bookmark counts, but provides no explicit guidance on when to use this tool over alternatives such as 'get-tags' or 'get-tag-bookmarks'. No exclusions or alternative names are mentioned, so the usage context is only implied.

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