Add Labels

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

With annotations already declaring readOnlyHint=false and destructiveHint=false, the description adds real value: it discloses that nonexistent labels get created (an implicit mutation beyond the page) and that 'the page body is not changed', scoping the blast radius. It stops short of noting permission requirements or the 25-label cap behavior.

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 clauses with zero waste: action, side effect, scope guarantee, and prerequisite. Front-loaded with the action and side effect before the version note.

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 two-parameter mutation with an output schema and annotations, the description covers action, side effect, and scope. Only minor gaps remain (permission needs, duplicate-label handling), so it is nearly complete but not exhaustive.

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 100%, so page and labels are fully documented in the schema, including format and lowercase storage. The description adds only the label-creation semantic, not parameter syntax, so the baseline 3 applies.

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 ('Add labels to a page') plus a notable side effect (missing labels are created). It is clearly distinct from siblings like remove_label and list_labels, though it never names them.

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 version prerequisite ('Needs Docmost 0.90 or newer') is genuine usage context, but there is no explicit when-to-use / when-not guidance or reference to the alternative label tools (remove_label, list_labels, find_pages_by_label). Usage is only implied.

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