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

Adds substantial context beyond the annotations: default gray color, case-insensitive duplicate detection that returns the existing label with created=false, and the requirement to be a full workspace member rather than a guest. These behavioral details are exactly what an agent needs for a mutation tool with no output schema.

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 compact and front-loads the create/update distinction, with important constraints following in a logical order. It is slightly dense with multiple clauses, but nearly every sentence carries operational value.

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?

Covers the mutation's scope, required and optional fields, default behavior, duplicate handling with a created=false return signal, and permissions. Given there is no output schema, this is complete enough for an agent to call the tool correctly without guessing.

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 carry parameter meaning, and it does: id toggles create vs update, name is required on create, color is optional with hex format and a default, and workspaceId is optional. All four parameters are meaningfully explained.

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?

States a specific verb and resource: creates a label when no id is given, or renames/recolors it when an id is present. It also disambiguates scope by stating labels are workspace-wide, not project-level, which separates it from save_project_label and delete_label siblings.

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?

Explicitly routes create vs update based on the presence of id, and redirects label assignment to save_issue with labelIds/addLabelIds. It does not explicitly name save_project_label as the alternative for project-scoped labels, though the workspace-scope sentence implies that distinction.

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