accelo_create_tag

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

No annotations are provided, so the description carries the full burden. It does not say whether tag names must be unique, what happens on a duplicate name, whether the tag is globally available, or what permissions/error behavior to expect. Only the 'required' nature of name is disclosed.

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 body is brief and front-loaded with the core action, but it is framed as a Python-style Args docstring rather than prose, and no sentence addresses when to use the tool. It is minimally structured without padding.

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 mutation tool with zero annotations, no output schema, and 0% schema description coverage, the description is incomplete: it omits return shape, duplicate handling, and side effects. An agent has just enough to attempt the call but not to predict its behavior.

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. It does clarify that 'name' is the tag name and required, and that 'fields' selects additional fields to return, but it adds no format, length, or uniqueness constraints for either parameter.

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 new tag'), which is unambiguous. However, it makes no attempt to differentiate from sibling tag tools like accelo_list_tags or accelo_count_tags, and there is no mention of scope or duplicates.

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?

There is no guidance on when to use this tool versus alternatives or prerequisites; the only usage-relevant statement is that name is required. An agent must infer the context entirely.

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