query_seo_experts

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

No annotations are provided, so the description carries the full burden. It discloses output format ('Returns actionable tactics each linked to the expert's original source video') and implies a read-only operation ('Query'). It does not mention pagination or rate limits, but these are not critical for a simple query 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?

The description is three sentences, front-loaded with the core purpose, and contains no redundant or filler language. Every sentence contributes meaningful information about what the tool does, how to filter, and what it returns.

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?

For a simple query tool with no output schema, the description sufficiently covers the return format and available filters. It omits the default limit behavior, but the schema documents the limit parameter, and the absence of nested objects or required params keeps complexity low.

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 100%, giving a baseline of 3. The description adds value by explicitly stating filters can be combined ('and/or') and enumerates the topic options, exceeding the schema's per-property descriptions.

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 opens with a specific verb+resource: 'Query real SEO experts' distilled tactics.' It clearly distinguishes from siblings (list_seo_experts and get_expert_pov) by emphasizing filtered tactic retrieval with topic, keyword, and expert slug options.

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?

Provides clear context: this tool is for querying/filtering tactics, not for listing experts or getting a single POV. However, it does not explicitly name alternatives or state when not to use it, only implying the use case through filter descriptions.

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