Add a guest

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

With no annotations, the description carries the transparency burden. It discloses that fit scoring runs asynchronously and advises checking list_guests later, which is key behavioral information. It doesn't cover all edge cases like error handling or idempotency, but the most important behavior is surfaced.

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 three sentences, each with distinct value: purpose, API wrapper, and async behavior guidance. There is no fluff or redundancy, and the key information is front-loaded.

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?

The tool has no output schema, but the description covers the main use case and a key behavioral nuance (async fit scoring). It lacks explicit return-value details, but the follow-up guidance compensates. The context is sufficient for an agent to understand the tool's role and next steps.

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 input schema provides descriptions for all 7 parameters (100% coverage), and the tool description does not add parameter-specific semantics beyond that. The description's mention of 'discover stage' is a general context, not tied to a parameter, so baseline 3 applies.

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 clearly states 'Create a new guest in the discover stage,' providing a specific verb, resource, and stage. It also maps to the underlying API endpoint (POST /api/v1/guests), and the action is distinctly different from sibling tools like list_guests or update_guest_stage.

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 description gives clear context for using the tool to create a guest and provides follow-up guidance to call list_guests or the detail endpoint to see fitScore. It doesn't explicitly exclude alternatives, but the create action is unambiguous among siblings.

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