vibo_join_event

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

Describes join as a confirm-gated mutation, which aligns with annotations (readOnlyHint=false). Adds context beyond annotations: confirms gating behavior and return value.

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?

Two sentences, front-loaded with main action. No fluff. Every sentence adds value.

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?

Covers key aspects: how to join, link format, confirm gate, return value. Lacks error handling but sufficient for core usage.

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%, baseline 3. Description adds meaning: link is a share URL or hash, confirm must be true to proceed. Clarifies the confirm parameter's role as a gate.

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?

Clear verb 'Join', specific resource 'event', method via share link/hash, and return value (event id). Distinguishes from sibling tools like vibo_get_event or vibo_leave_event.

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 when to use: to join an event you were invited to via share link. Implicitly excludes other actions but lacks explicit alternatives or when-not-to guidelines.

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