search_in_collective

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

No annotations provided, so the description carries full burden. It fails to disclose whether the search is full-text, case-sensitive, supports partial matches, or returns paginated results. The return 'metadata' is vague without specifying fields.

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 concise with two sentences, but could be more structured (e.g., bullet points for clarity). It is not overly verbose.

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, the description should specify the return format (e.g., page IDs, titles, snippets). It also lacks details on search behavior (e.g., exact match vs. full-text), making it incomplete for an agent to use effectively.

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 documentation coverage is 50% (only 'query' has a description). The description adds context that 'collectiveId' identifies the collective and 'query' searches content, but does not fully compensate for the missing schema description on collectiveId.

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 the verb 'Search for pages by content' and specifies the resource as 'within a specific Collective', with a clear output of 'matching page metadata'. It distinguishes from sibling tools like 'search' (global scope) and 'list_pages' (no search).

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 implies usage when searching within a specific Collective, but lacks explicit guidance on when not to use it (e.g., for global search or listing) and does not mention alternatives.

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