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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool creates a booking, which implies a write operationtons. It also discloses the authentication requirement (authToken), which is a key behavioral aspect. The description does not detail side effects (e.g., whether it's idempotent, if it triggers notifications) or the response format, but given the lack of annotations, it does a reasonable job of setting expectations for a create operation.

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 concise, consisting of two sentences. The first sentence states the core action and subject, and the second provides a critical usage constraint (authentication). It is front-loaded with the main purpose and adds a key caveat without any fluff. Every word earns its place.

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?

Despite having no output schema and no annotations, the description is sufficient for an agent to understand what the tool does and its key prerequisite (authentication). The tool is a straightforward create operation, and the description covers the essential context. The schema handles parameter details, and the description does not need to explain return values since it is a create action and the caller likely expects a confirmation. The context is complete for safe invocation.

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 schema description coverage is high (88%), so the schema already documents most parameters. The description adds value by stating the authentication requirement for the authToken parametereur, which is not explicitly described in the schema (the schema says 'Sharaloge customer JWT auth token' but the description emphasizes 'requires the customer to be authenticated'). This adds context beyond the schema, but most parameter meanings are already covered by the schema, so a score of 4 is appropriate.

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 the tool's purpose: creating a booking reservation with a Sharaloge artist for a given date and time. It identifies the specific resource (booking) and the action (create), and the mention of 'Sharaloge' distinguishes it from generic booking tools. The description is specific enough to differentiate it from the sibling tools (get_artist_profile, search_artists) which are about viewing artist data, not creating bookings.

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 provides a clear context for when to use this tool: when creating a reservation with a Sharaloge artist. It also states a prerequisite (customer must be authenticated with authToken), which guides the agent on when it's appropriate to call the tool. However, it does not explicitly state when NOT to use this tool or mention any alternatives (like using search_artists for finding artists before booking), but the purpose is clear enough to infer.

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