add_label

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

The description reveals the non-obvious behavior that adding a label means copying the email into a Labels/<name> folder, which is valuable context beyond the tool name. However, with no annotations, it does not disclose prerequisites such as the label needing to exist, potential side effects, or error behavior.

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 one tight sentence that front-loads the action and then adds an important parenthetical clarification. There is no filler or redundant restating of the tool name.

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 description captures the core operation and the Bridge-specific representation, but it leaves parameter semantics unexplained and does not guide the agent toward related tools for label creation or removal. Given the schema provides defaults for account and mailbox, the tool is usable, but the description alone is not fully complete.

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 0%, so the description must compensate for parameter meaning. It only clarifies that 'label' maps to a folder name in Bridge, but it does not explain 'uid', 'account', or 'mailbox'. Required parameters are otherwise undocumented.

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 states a clear verb and resource: 'Add a ProtonMail label to an email.' It also clarifies the underlying mechanism, 'copies it into the Labels/<name> folder,' which distinguishes this from create_label and remove_label.

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 when to use the tool by saying it adds a label to an email, and it gives useful context about how Bridge represents labels. However, it does not explicitly name alternatives like create_label for creating a label or remove_label for removing one, nor does it state when not to use it.

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