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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavior ('Sorted by recency', substring matching scope), but omits pagination/limit behavior and return shape, leaving meaningful gaps for a search tool.

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?

Four terse sentences, front-loaded with the core action and scope, and the invocation constraint is placed last where it is easy to check. No filler.

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?

With no output schema the description reasonably carries the burden, and it covers matching scope, sort order, and the required-input constraint. Missing pagination/limit semantics and any hint about result volume are the only shortfalls.

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 coverage is 75% and the description adds real meaning by stating what q matches against (body sections, topics, type, references) — the schema only says 'case-insensitive substring to match' without naming the searched fields. It does not cover the undocumented limit parameter, which keeps it from a 5.

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?

States a specific verb ('Substring search') and resource ('AI-section posts'), with the scope qualifier implicitly separating it from the sibling search_human_posts. It never names that alternative explicitly, so the differentiation is inferable rather than stated.

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?

Gives a real precondition ('At least one of q, category, type is required') that tells the agent how to invoke it validly, but offers no when-to-use/when-not guidance and never points to search_human_posts or other siblings as alternatives.

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