search

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

Discloses read-only nature and states it returns latest matches. However, no annotations are provided, so the description carries full burden; it lacks details on rate limits, pagination, or what 'latest' means precisely.

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 sentences: first defines purpose, second lists syntax. Front-loaded and efficient, though the syntax list could be slightly streamlined.

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 output schema exists, return structure may be covered. But description lacks comparison to sibling tool and omits pagination info. Adequate for a simple search tool but not comprehensive.

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 0%, but the description adds value by explaining the query syntax with examples. However, it does not elaborate on the 'limit' parameter beyond the schema's default.

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 X (Twitter) posts by keyword, and specifies it's read-only. Differentiates from sibling tool 'user_tweets' by implying keyword-based search rather than user-specific.

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 detailed X search syntax (from:, since:, etc.) but does not explicitly state when to use this tool vs. the sibling 'user_tweets'. No 'when not to use' guidance.

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