plan_search

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

No annotations are provided, so the description must disclose behavioral traits. It mentions authentication requirements but does not explicitly state whether the operation is read-only or has side effects. The context implies a read operation, but transparency is lacking.

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 at two sentences, but it sacrifices completeness. It front-loads the core purpose but omits parameter details, requiring the agent to infer from schema alone.

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 tool's 3 parameters and lack of output schema or annotations, the description is incomplete. It does not explain parameter constraints (e.g., limit default, service filtering), output structure, or pagination behavior, making it insufficient for reliable tool use.

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?

The schema has 3 parameters with 0% description coverage. The tool description fails to explain the meaning or usage of any parameter (query, limit, service). This is a significant gap for an agent to correctly invoke the tool.

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 action ('Search') and the resource ('configured plan bank'), and lists specific fields returned (service, title, url, line, snippet). It also references sibling tool plan_get for comparison, helping to differentiate.

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 provides a prerequisite ('Requires plan_configure + NOTION_TOKEN') but does not explicitly state when to use this tool over alternatives like plan_get. The comparison to plan_get is implied but not expanded into a clear when-to-use or when-not-to-use guideline.

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