Search Specific Event Source

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds useful source-level context (do215 = indie/arts/nightlife, visitphilly = tourism, eventbrite = ticketed) but says nothing about pagination, deduping, or result volume limits beyond the limit param.

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?

Front-loaded with purpose and routing guidance before the Args and source catalog, and each source line carries distinct selection value. Slightly padded by restating limit's default and response_format enum that the schema already documents.

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?

No output schema exists, so the description should set expectations for what comes back; it mentions markdown/json format but never describes the returned event fields. The truncated source enum also makes the definition incomplete relative to the actual parameter domain.

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 Args block restates limit's default and query/response_format without adding syntax beyond the schema. More seriously, it declares source is 'one of do215, visitphilly, eventbrite' while the schema enum permits six values (also whenwherewhat, uwishunu, phillymag), so the description actively under-informs and could steer an agent away from valid sources.

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 from a specific Philadelphia event source') and explicitly scopes it against the broader aggregation behavior. An agent can distinguish it from philly_search_events (all sources) without opening either schema.

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 second sentence gives explicit when-to-use guidance ('search only one source rather than aggregating from all sources'), which implies the alternative sibling philly_search_events. It stops short of naming that sibling explicitly, so routing still requires a small inference.

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