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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the return shape (including settings such as the attendee limit) and an auth prerequisite ('Needs the user's Cotlet API key with access to this app').

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 and short, but the field enumeration is duplicated: 'title, description, time, venue or online link, hosts, fee and settings' is then restated as 'its full description, venue or online link, hosts and settings such as the attendee limit.' One of the two sentences is largely wasted space.

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, the description carries the burden of describing returns and does so with concrete fields, plus auth requirements and sequencing relative to copy_event/update_event. Minor gaps remain (no mention of error behavior or what happens with an unknown id), but nothing essential for a correct call 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?

Single parameter with 100% schema description coverage ('Event ID from list_events'), so the schema carries the semantics. The description adds nothing parameter-specific beyond the notion of fetching one event, which is the expected baseline when coverage is complete.

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 (get) and resource (one Meetup event) and enumerates exactly what is returned: title, description, time, venue or online link, hosts, fee and settings. The phrase 'one event' separates it from the sibling list_events, so an agent can route correctly without opening schemas.

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?

Explicitly states a use condition: 'Use it before copy_event or update_event,' naming two concrete siblings. It gives no when-not guidance (e.g. that list_events should be used to find an id first), so it falls short of full alternative routing.

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