changedetection_create_tag

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

Annotations already declare this is a non-read-only, non-idempotent write. The description adds important behavioral detail beyond annotations: confirm must be explicitly set to true to execute, and omitting it yields a dry-run preview. It does not describe auth requirements or return behavior, but the dry-run semantics are a meaningful addition.

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?

Three short sentences, front-loaded with the core action, followed by the endpoint, required field, and dry-run caveat. There is no wasted text.

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?

For a tool with 56 parameters, nested objects, no output schema, and sparse schema descriptions, the description is far too brief. It explains the dry-run pattern but not what the many optional fields do, what kind of tag settings are supported, or what happens on creation.

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?

The schema has 56 parameters and only 25% description coverage. The description mentions only two: title (required) and confirm (dry-run). It does not explain the many tag-level or watch-like settings in the schema, leaving most parameters undocumented in both description and 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 states a specific verb and resource: 'Create a tag.' That clearly distinguishes it from delete_tag, update_tag, and get_tag. It does not explicitly contrast with siblings, but the purpose is unambiguous.

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?

It says 'Requires title' and explains that omitting confirm produces a dry-run, which is useful operational guidance. However, it never says when to use this instead of update_tag or list_tags, and gives no exclusions or prerequisite context.

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