Events

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

Adds meaningful context beyond the annotations: it discloses credit consumption, the confirm=true gating requirement, and clarifies that the non-read-only POST is 'read-like' and 'does not publish to social platforms' — resolving the apparent tension with readOnlyHint=false. It stops short of describing return shape or pagination 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?

Purpose is front-loaded in the first sentence, followed by the source example and the operational caveats. It is compact, though the inline example link is somewhat verbose relative to the routing information conveyed.

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 fetch tool with no output schema, the description covers purpose, the source, credit cost and the confirm requirement, while annotations carry the safety profile. It is nearly complete, missing only any note on result format or pagination expectations.

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 100%, so all five parameters are already documented in the schema, and the description adds no syntax or format detail beyond restating confirm=true. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource with scope ('Get the events of a city') and grounds it with an example URL of the data source. It is clear what the tool returns, but it does not distinguish itself from the similar sibling facebook_events_search_events, leaving the agent to infer the difference.

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 a key usage precondition ('Potentially consumes paid API credits; requires confirm=true'), which tells the agent when a call is safe to make. However, it gives no guidance on when to choose this over alternatives like facebook_events_search_events or facebook_events_event_details.

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