get_tag

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

No annotations are provided, so the description carries the full burden. 'Get' weakly implies a read-only operation, but nothing is said about permissions, error behavior for unknown ids, or whether board_id must match the tag's board.

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?

Extremely short and front-loaded, but the brevity reflects under-specification rather than efficient communication. There is no wasted text, yet every sentence that should be there is absent.

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?

An output schema exists, so return values needn't be described. But with zero annotations, zero schema descriptions, and no usage context, the definition leaves an agent guessing about scope, preconditions, and the board_id/tag_id relationship.

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% — parameters carry only bare titles ('Tag Id', 'Board Id'). The description adds no meaning, such as why a tag lookup requires board_id alongside tag_id or what format ids take. The names are self-explanatory enough to avoid a 1.

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?

States a specific verb and resource ('Get one tag'), which distinguishes it from list_tags and get_item_tags by implying single-resource retrieval. However, it does not clarify key scope questions such as whether 'one tag' means a tag definition on a board versus a tag's occurrences on items, leaving ambiguity against several sibling tools.

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?

No guidance on when to use this versus list_tags, get_item_tags, get_items_by_tag, or attach/detach_tag. The agent must infer that this fetches a tag definition by id rather than tag usage.

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