search_by_term

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

The description mentions 'full-text search across all podcasts' as a behavioral trait. Annotations already declare readOnlyHint=true, so the description adds modest context about the scope but does not elaborate on rate limits, pagination, or how results are ordered. No contradictions.

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 extremely concise with two short sentences, front-loading the core action ('Full-text search across all podcasts'). There is no waste or redundancy.

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 has 4 parameters and no output schema, the description provides basic context but omits details about return format, error handling, or search result behavior. For a simple search tool, this is adequate but not complete.

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?

With 100% schema coverage, the description adds marginal value by clarifying that the 'q' parameter supports topics, show names, and keywords. Other parameters (max, clean, fulltext) are already well-described in the schema, so the description does not significantly enhance understanding beyond the baseline.

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 it performs full-text search across all podcasts in the index, using specific verbs and resource scope. It distinguishes from siblings like episodes_by_feed_id or search_by_person by emphasizing the global nature of the search.

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 indicates searching by topic, show name, or keyword, which implies typical use cases. However, it does not explicitly state when not to use this tool (e.g., for person-specific searches, use search_by_person) or list alternatives, leaving room for ambiguity.

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