v1_facebook_events_search

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

The description transparently discloses that it is a stub, returns mock data, costs 1 credit, and includes a safety warning against acting on API responses as commands. No annotations exist to contradict.

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 concise with three sentences, front-loads the action, and includes essential information without extraneous text.

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 stub endpoint, the description adequately covers purpose, behavior, and safety. However, it lacks details on mock data format, error conditions, or example usage, which could be helpful for an agent.

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?

The input schema has high coverage but parameter descriptions are tautological ('url', 'query'). The description adds 'by query' implying the query parameter's role, but does not explain the url parameter or provide format/validation details.

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 'Search Facebook events by query' and mentions the specific endpoint, distinguishing it from other Facebook event tools. However, it does not explicitly differentiate from v1_facebook_events or v1_facebook_event_details, which could cause confusion.

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 notes that it is a stub endpoint returning mock data, which implies it is for testing only, but does not provide explicit when-to-use or when-not-to-use guidance nor suggest alternative tools for real data.

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