Add Tags to Note

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

Annotations already mark the tool as idempotent and open-world. The description adds that tags are added at the beginning of the note, which is behavioral info beyond annotations. It does not clarify if new tags are created automatically (openWorldHint) or if duplicates are allowed.

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 concise with two sentences, no unnecessary words, and front-loaded with the core action.

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, the description covers basic functionality and a reference to list tags. However, it lacks details on error scenarios (e.g., note not found) and behavior with new tags (openWorldHint).

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% and the description adds minimal extra meaning: it notes tags are added at beginning, but the schema already details tag format without '#'. The id parameter is fully described in 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 the verb (add) and resource (tags to a Bear note), and specifies that tags are added at the beginning. It differentiates from siblings like bear-list-tags and bear-delete-tag.

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 advises using bear-list-tags to see available tags, providing a helpful prerequisite. However, it does not explicitly mention when not to use this tool or contrast with alternatives like bear-rename-tag.

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