add_page_labels

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

Annotations already declare readOnlyHint=false and destructiveHint=false, which is consistent with the additive write behavior. The description adds genuinely useful behavioral context by stating that names are normalized to lowercase kebab-case, which affects how inputs are interpreted.

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 two short sentences with no filler. The primary action is front-loaded, and the normalization behavior is a relevant detail that earns its place.

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 simple two-parameter write tool with annotations present and no output schema, the description covers the essential invocation details. It is only slightly incomplete in not addressing duplicate-name behavior or idempotency, but neither gap prevents a correct call in the common case.

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 only 50%, with names lacking a description. The description compensates by explaining that names are labels and that they will be normalized to lowercase kebab-case. page_id already has a schema description ('Page UUID or slugId'), so the description adds meaningful semantics where the schema is silent.

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 ('Add'), a concrete resource ('labels to a page'), and the scope ('one or more'). It is clearly distinguishable from the sibling tools list_page_labels and remove_page_label, which perform opposite operations.

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 purpose clearly implies when to use the tool: whenever labels need to be added. However, it does not explicitly contrast with list_page_labels or remove_page_label, nor does it state any conditions where another tool should be used instead.

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