tag

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as read-only ('info'), but does not confirm non-destructive behavior or explain the boolean parameters 'total' and 'verbose' that alter output.

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 short (three words) but lacks structure. It is not a complete sentence and omits crucial details. Effective conciseness balances brevity with informativeness, which is absent here.

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?

Given no output schema, low schema coverage, and no annotations, the description is severely incomplete. It does not explain the return format, behavior of optional parameters, or any constraints, making it inadequate for an agent to invoke correctly.

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 only 25% (only 'vault' described). The description adds no information about parameters, leaving the required 'name' and the boolean flags undefined. This fails to compensate for low 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 tag info' specifies a verb and a resource, providing basic clarity. However, it does not differentiate from the sibling tool 'tags' (plural), which might list tags. A more specific description, such as 'Get details about a specific tag by name,' would improve distinction.

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 offers no guidance on when to use this tool vs alternatives like 'tags' or other related tools. It lacks context on prerequisites, such as whether the tag must already exist, or which scenarios are appropriate.

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