scrape_fabrizio_tweets

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

No annotations are provided, so the description carries full burden. It mentions 'optimizado' but discloses no behavioral traits like rate limits, authentication needs, data mutability, or termination behavior. Critical gaps for a scraping tool.

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?

A single, efficient sentence with no extraneous words. Though in Spanish, it is front-loaded with the core action. Could be improved with a brief structuring of actions.

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 complexity (multiple actions, no output schema, scraping scope), the description is insufficient. It does not explain the difference between scrape, recent, and vip actions, nor what data is returned. Important context is missing.

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%, so each parameter already has a description. The tool description adds no additional meaning about how count, hours, action, or save_to_database behave or interact. Baseline of 3 is appropriate.

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 scrapes tweets of Fabrizio Romano using TwitterAPI.io optimized, identifying the verb, resource, and method. However, it does not explicitly distinguish itself from the sibling 'search_fabrizio_tweets', though the action parameter adds nuance.

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 guidance on when to use this tool versus alternatives like search_fabrizio_tweets or test_foxbrizrio. It lacks when-to-use, when-not-to-use, or alternative references.

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