tag_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get details,' which is a restatement of the name and does not disclose whether the operation is read-only, what response format to expect, error conditions, or any side effects. For a simple getter, more context (e.g., 'read-only' or 'returns tag name, color, ID') is needed.

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 that is front-loaded and contains no unnecessary words. It is maximally concise and well-structured.

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?

The tool is simple with one parameter and no output schema, but the description is minimal. It does not clarify what 'details' are returned, nor does it differentiate from tag_list, which serves as a sibling. Given the absence of an output schema and annotations, the description is adequate but leaves some ambiguity about the response structure and its relationship to similar tools.

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% (the 'id' parameter is described as 'Tag ID'), so the schema already documents the parameter. The description adds no further meaning about the parameter, which meets the baseline for high schema coverage.

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 details of a specific tag in Toshl Finance' uses a specific verb ('GET') and resource ('details of a specific tag'), clearly distinguishing it from siblings like tag_list and tag_create. It is concise and unambiguous about its function.

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: use when you need details of one tag. However, it does not explicitly state when to use this tool versus alternatives like tag_list, nor does it mention any exclusions or prerequisites. Guidance is only implied by the tool name and schema.

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