tag

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

No annotations are provided, so the description must fully disclose behavior. It covers the actions and their effects but does not mention side effects (e.g., whether remove is reversible) or permissions 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 well-structured with an action enumeration and parameter list. It is reasonably concise, though the 'Args' section could be slightly tightened.

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 the complexity (5 parameters, 1 required) and presence of an output schema, the description covers the core functionality but omits edge cases (e.g., duplicate tags, empty results) and does not explain the output format.

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%, but the description adds meaning by explaining each parameter's purpose and providing examples (e.g., 'e.g. "ai,research,llm"' for tags). This compensates for the missing schema descriptions.

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 tool manages notebook tags with four actions: add, remove, list, select. It distinguishes from sibling tools like notebook_query by focusing on tag operations rather than general notebook queries.

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 explicitly lists each action and when parameters are required, but does not provide guidance on when to choose this tool over alternatives (e.g., use select for tag matching vs notebook_query for other criteria).

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