Apply Tag

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

The description adds value beyond annotations by disclosing that the tool can execute 'completion/archive/swap actions' optionally, which gives context to the destructiveHint and idempotentHint. However, it does not elaborate on the nature or consequences of these actions, leaving the full behavioral impact vague. No contradiction with 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 a single, front-loaded sentence of 14 words. It efficiently conveys the primary function and optional behavior without redundancy or filler.

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 has 5 parameters, no output schema, and complex side effects. The description is insufficiently complete for an agent to understand prerequisite steps, parameter dependencies (e.g., when confirm is required), return values, or the detailed effects of apply_actions. It leaves significant gaps for safe invocation.

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?

With 0% schema description coverage, the description must compensate but only explains the apply_actions parameter implicitly via 'optionally execute its completion/archive/swap actions.' It completely omits the meaning or purpose of tag_id, entry_id, bundle_id, and confirm. The description provides minimal semantic value beyond the raw schema.

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 clearly states a specific action: 'Apply a tag; optionally execute its completion/archive/swap actions.' This distinguishes it from tag CRUD siblings like create_tag, update_tag, remove_tag, and delete_tag by implying attachment of an existing tag. However, it does not explicitly state what the tag is applied to (e.g., an entry), leaving some ambiguity for the agent.

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 bundled_remove_tag or bundled_update_tag. There is no mention of context, prerequisites, or when not to use it. The description only explains what it does, not when to choose it.

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