search_pages

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

With no annotations provided, the description must disclose behavioral traits like read-only nature, authentication needs, or result behavior. It does not: it only says 'Search' and 'filter', leaving agents to infer that this is a read operation without explicit confirmation or additional context (e.g., what happens with no results).

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 very short (two sentences) and front-loaded with the purpose. Each word earns its place, but it could be slightly more informative without adding bloat, hence a 4 rather than 5.

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?

Given the complexity (7 parameters, no output schema, no annotations), the description is insufficient. It lacks essential context such as search behavior (full-text? case-sensitive?), error handling, pagination hints (though in schema), and prerequisites. An agent would need to guess or experiment.

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?

While the input schema covers all 7 parameters with detailed descriptions (100% coverage), the description adds no meaning beyond the schema—it merely repeats 'keyword, note, or tag' which is already evident. The baseline of 3 is reduced because the description fails to enrich parameter understanding.

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 clearly states 'Search NotePM pages' with a specific verb and resource, and lists filtering capabilities that distinguish it from sibling tools like get_page (single page) and create_page. However, it does not explicitly contrast with other search-related tools, so it falls short of a 5.

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 description mentions filtering options but provides no guidance on when to use this tool versus alternatives, such as get_page for a specific page or list_folders for navigation. No exclusion criteria or context-specific recommendations are given.

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