getTag

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

Annotations already declare the tool as read-only, non-destructive, and idempotent. The description adds value by specifying the return format 'status, message with array' and handling of not-found cases (empty or 404). No contradiction with annotations.

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 concise, with purpose front-loaded. Each sentence serves a distinct purpose (overview, use case, required field, alternative, return format). No unnecessary text.

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 get-by-id tool with rich annotations, the description covers all needed context: when to use, required parameter, alternative, return format, and error behavior. No output schema exists, but return format is explained adequately.

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?

With 0% schema description coverage, the description only repeats the required id parameter. It does not add any further meaning such as constraints, valid values, or formatting instructions.

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 'Get a single tag' and 'Fetch a single tag record', specifying the verb and resource. It distinguishes from sibling tool listTags by stating 'fetching one tag by ID' and providing a 'See also' reference.

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?

Explicit 'Use when: fetching one tag by ID' and 'Required: id' provide clear guidance. The 'See also' reference to listTags offers an alternative for enumerating many tags.

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