texttv_search

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, so the carrying burden is lower. The description adds that it searches across all pages, but does not disclose any other behavioral traits such as pagination, rate limits, or result structure. It suffices but adds minimal value beyond annotations.

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 two concise sentences, each serving a purpose: stating the core function and adding the optional filter. No redundant or extraneous information.

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 absence of an output schema, the description does not explain what the search returns, which is a gap. However, the parameters and annotations are well-covered otherwise. The description is adequate for a simple search tool but could be enhanced with return format details.

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%, so the schema already documents all parameters. The description repeats the category options and implies that 'query' searches across pages, but adds no new meaning beyond what is in the schema. It does not elaborate on maxResults or includePlainText.

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 uses the verb 'search' and identifies the resource as 'SVT Text-TV pages', clearly stating the tool's action and scope. It distinguishes from sibling tools like texttv_get_news or texttv_browse_category by indicating this is a general search across all pages, with optional category filtering.

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 mentions optional category filtering, which gives some context on when to use it, but does not explicitly state when not to use it or provide alternatives from the sibling list. An AI agent could infer that for a specific category, dedicated tools might be better, but the description lacks explicit guidance.

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