search_hashtag

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The description only states it searches videos, implying a read operation, but does not mention any potential side effects, rate limits, result limits beyond the default, or permissions required. Minimal transparency.

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 a single short sentence with no redundant words. It is concise and front-loaded. However, some information that could improve clarity (like usage guidance) is missing, which slightly lowers the score from 5.

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 tool with 2 parameters and no output schema, the description is somewhat complete in stating the core functionality. However, it lacks context about the return format, pagination, or how it differs from sibling tools like search_videos. A more complete description would help the agent understand the scope.

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% for both parameters (hashtag, max_results), and the description adds no additional semantic information beyond what is in the schema. According to guidelines, baseline is 3 when coverage is high, and the description does not provide extra value.

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 'Search videos by hashtag' clearly states the verb (Search), the resource (videos), and the specific filter (by hashtag). This distinguishes it from sibling tools like search_videos (which may search by other criteria) and get_trending_hashtags (which lists trending hashtags, not videos).

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 provides no information on when to use this tool versus alternatives like search_videos. It does not mention any exclusions, prerequisites, or comparative advantage. The agent is left without guidance on selecting this tool over siblings.

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