wikijs_search_pages

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

No annotations provided; description only says 'return path/title summary'. Missing behavioral details: read-only nature, case sensitivity, fuzzy search, pagination, error handling, or what happens with empty 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?

Single sentence front-loads purpose and output. Efficient but could use slight structure for parameters. No wasted words.

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 no output schema, description partially explains return format (path/title summary). Lacks details on result array structure, empty results, or performance. Adequate for simple search.

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 descriptions cover all 3 parameters (100% coverage). Description adds no extra parameter meaning; it focuses on output. 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?

Clearly states verb 'search', resource 'pages', method 'by keyword', and output 'path/title summary'. Differentiates from sibling list and get tools but doesn't explicitly contrast with list_pages or search_tags.

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?

No guidance on when to use vs alternatives (e.g., list_pages for browsing, search_tags for tags). Only implies purpose for knowledge lookup, but no when-not-to-use or context.

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