Get Tag

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the list of returned fields, but it omits that these fields require opt_fields (schema notes defaults are only gid and resource_type), so the description may overstate the default return. No contradiction with annotations, but this is a gap.

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?

Two sentences, front-loaded with the main purpose, and includes a useful pointer to a sibling tool. No wasted words.

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 read-only tool with full schema coverage and strong annotations, the description is mostly complete. However, the potential ambiguity about default vs. opt_fields returns means it isn't fully self-contained; an agent might not realize that the listed fields are not all returned by default.

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 has 100% coverage with detailed descriptions for both parameters, including where to find tag GIDs and useful opt_fields values. The description adds minimal new info beyond pointing to asana_get_tags_for_workspace, and it doesn't clarify the relationship between opt_fields and the listed returned fields.

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 a specific verb ('Get') with a clear resource ('full details for a single tag') and method ('by GID'). It distinguishes from sibling tools by referencing asana_get_tags_for_workspace for finding GIDs, clearly communicating what the tool does.

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?

Explicitly states when to use this tool (when you have a tag GID and need full details) and directs to asana_get_tags_for_workspace to find GIDs. The param schema reinforces this by telling users where to get GIDs, providing clear alternative guidance.

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