publish_event

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

With no annotations, the description discloses multi-minute execution, shared-state /tmp/draft_event.json serializing events, and concurrency limit of one, plus a warning to wait for the result.

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 purpose, followed by structured preconditions and notes; every sentence adds non-redundant information.

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 multi-step side-effect-heavy tool with no output schema, it covers actions, preconditions, excluded features, timing, concurrency, and recovery path.

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 is empty with zero parameters; description explains the tool operates on pre-existing draft state and refers to shared state path, clarifying what 'inputs' are implied.

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?

Description opens with 'Phase 2: publish the drafted event' and enumerates concrete actions (Drive folder, event-details.json, Calendar event with Meet link, Luma listing, social queues), clearly distinguishing it from drafting and cleanup.

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?

Explicit preconditions (draft exists, set_registration_link succeeded), exclusion (Meetup/poster not automated), and a pointer to cleanup_state for abandonment.

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