Search SGU news items

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

No annotations provided, but description adequately discloses read-only search behavior, return format, and that each news item is linked to an episode. Does not mention pagination or sorting, but these are minor gaps given the simplicity. 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?

Two efficient sentences plus a concise return fields note. No unnecessary words. Front-loaded with action and scope.

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 search tool with two parameters, the description provides complete information: purpose, usage, and return fields. No output schema, but return fields are listed. Fully adequate for agent 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 coverage is 100% with clear parameter descriptions. Description adds no additional detail beyond schema, so baseline score of 3 is appropriate. The parameter semantics are fully captured in the schema.

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?

Clearly states it searches science news items, each a topic page tagged with episode number. Distinguishes from sibling tools like search_episodes and search_transcripts by specifying the resource type and return fields (topic title, episode number, link).

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?

Explicitly provides usage scenarios: 'find which episode covered a topic' and 'survey coverage of a subject.' Implicitly distinguishes from alternatives by focusing on news items. Could be improved by explicitly stating when not to use it (e.g., for episode search).

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