search_posts

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

With no annotations, the description carries the burden. It does disclose meaningful behavioral constraints: search is limited to titles, recency, and a maximum of 10 list pages. However, it does not explain ordering, matching behavior, how 'recent' is determined, or what happens at page limits.

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 a single, front-loaded sentence with no filler. Every word adds scope or constraint information, making it appropriately sized for the tool's simplicity.

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?

Although the tool has a simple flat schema and an output schema, the description lacks essential context about the required 'board' parameter and the meaning of 'list pages.' With no annotations and zero schema description coverage, the description is not complete enough for confident invocation.

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 0%, so the description must compensate. It partially clarifies 'query' (searches post titles) and 'pages' (up to 10 list pages), but it never explains the 'board' parameter, which is required. This leaves a meaningful semantic gap.

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), the resource (post titles), and a scoping constraint (recent, up to 10 list pages). It is distinct enough from the siblings, though 'list pages' is slightly ambiguous and does not explicitly contrast with list_posts or get_post.

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 gives no guidance on when to use this tool versus list_posts or get_post. There are no explicit conditions, exclusions, or alternatives, so the agent must infer the intended use context.

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