twspaces-get_tag

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds no behavioral information beyond the tool name—no mention of authentication, return payload, or any edge cases. It fails to add value beyond the structured 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 extremely concise with no fluff, but it is under-specified. It lacks any explanation that would help an agent understand the tool's purpose or context. Conciseness should not come at the expense of essential 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 get-by-id tool, the description is minimally adequate. The schema covers the parameter, annotations cover safety, and no output schema exists. However, the description fails to explain what a 'Spaces tag' is, whether the operation returns the tag directly, or any related context. Still, given the simplicity and good schema/annotation coverage, completeness is acceptable.

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 coverage is 100%: the single parameter 'id' has a clear description ('The ID of the tag to retrieve.'). The tool description adds no parameter semantics, but the schema fully documents the parameter, so the baseline of 3 applies.

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 'Get Spaces tag.' clearly identifies the action (get) and the resource (Spaces tag), distinguishing it from tag tools in other modules like twprojects-get_tag or twdesk-get_tag. However, it lacks any additional context about what a Spaces tag is or how it relates to Spaces.

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 is provided on when to use this tool versus alternatives such as twspaces-list_tags or twspaces-update_tag. The description gives no context, prerequisites, or exclusions.

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