Search Events

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

Adds behavior beyond the annotations: discloses that the call 'Potentially consumes paid API credits' and requires confirmation, and clarifies that 'Read-like POST requests do not publish to social platforms.' This resolves the tension between a POST and the destructiveHint=false annotation. It stops short of describing pagination or rate-limit behavior.

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 core purpose is front-loaded in the first sentence, but the inline documentation link is extraneous and the credit/confirm caveats are run together with the publishing note in one sentence. Adequate but not tightly structured.

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?

With no output schema and 100% schema coverage, the description covers the key operational caveats (credits, confirm, no social publishing). It does not explain the returned event shape or how cursor pagination behaves, which is a gap for a search tool.

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 the schema already documents query, cursor, account, and confirm. The description reinforces the confirm=true requirement and the credit-cost rationale, adding marginal value but no syntax or format detail beyond 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?

States a specific verb+resource ('Search for events by name'), which is clear on its own. However, it does not differentiate from sibling tools like facebook_events_events or facebook_events_event_details, leaving the agent to infer the boundary between searching, listing, and fetching details.

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 one concrete precondition ('requires confirm=true') and warns about credit consumption, which is useful routing context. But it gives no guidance on when to prefer this over facebook_events_events or facebook_events_event_details, and no exclusion conditions.

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