Find Pages By Label

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a version-gating requirement (Docmost 0.90+) that is not in any structured field, which is genuine extra context; it stops short of describing result ordering or pagination 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?

Two short sentences, the core listing behavior front-loaded and the version prerequisite trailing where it belongs. No filler.

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?

With an output schema present, full parameter documentation, and read-only annotations, the description covers what the agent needs to call it. The version prerequisite is a useful addition; only minor gaps around result scoping remain.

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 100%, so label, limit, cursor, and space_id are all fully documented upstream, making 3 the baseline. The description's 'in all spaces or in one' loosely reinforces space_id semantics but adds no syntax or formatting detail beyond the 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?

States a specific verb and resource: 'List the pages that carry a label,' with the scope qualifier 'in all spaces or in one.' An agent can distinguish this from list_pages and list_labels, though the description never names those siblings explicitly to sharpen the boundary.

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?

'Needs Docmost 0.90 or newer' gives a real prerequisite, and 'in all spaces or in one' implies the space_id filtering choice. However, it never says when to prefer this over list_pages, search, or list_labels, so alternative selection is left to inference.

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