Add a guest

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: this wraps POST /api/v1/guests and fit scoring runs asynchronously after creation. It also advises checking list_guests shortly after. Missing are details like required permissions or error handling, but the async behavior is a significant addition beyond schema.

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?

Three sentences, front-loaded with the core action, then the endpoint and async follow-up. Every sentence earns its place with no waste or redundancy.

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 the tool's moderate complexity (7 params, 4 required), full schema coverage, and no output schema, the description provides essential behavioral context: async fit scoring and a follow-up action. It is nearly complete, though it lacks explicit guidance on choosing this tool over siblings, which would enhance completeness.

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 description coverage is 100%, so the schema already documents all 7 parameters thoroughly. The description adds no parameter-specific meaning beyond what is in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Create a new guest in the discover stage.' It distinguishes from siblings like update_guest_stage and list_guests by specifying creation and the initial stage. An agent can immediately understand this tool's function.

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 implies usage by stating it creates a guest in the discover stage and suggests calling list_guests or the guest detail endpoint afterward to see fitScore. However, it does not explicitly say when to use this tool versus alternatives like update_guest_stage or draft_outreach_email. No when-not conditions are provided.

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