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

With no annotations, the description carries the full burden and discloses important behavior: Lagos/WAT time handling, a preview-before-confirm requirement, and post-success handling of the invite code. It stops short of covering permissions, error behavior, or broader side effects, so it is strong but not exhaustive.

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?

The description is front-loaded with the tool purpose and then lists only operational rules that matter. It is appropriately sized for a workflow-sensitive creation tool, though the internal jargon around step_18_body_from_* is slightly cryptic.

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?

Given no annotations and no output schema, the description does well by specifying the critical invite_code output handling and the preview/confirm workflow. It still does not describe the full return payload, error cases, or permission requirements, leaving some completeness gaps.

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%, so the parameter schema already documents all six fields, including WAT timing and name requirements. The description reinforces required guest names and warns against passing step_18_body_from_* hour fields, but adds limited meaning beyond the already-complete schema.

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?

The description opens with a precise verb and resource: 'Create a guest visit invite.' This is specific enough that an agent can distinguish it from all sibling tools, which are fetch/list/login operations rather than invite creation.

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?

It provides clear procedural guidance: collect both guest names before preview, always emit_display preview before Confirm, and do not pass step_18_body_from_* hour fields. It does not name alternative tools or explicitly state when not to use this one, but the workflow context is strong.

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