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

Annotations are all false and provide little safety context, so the description carries the burden of explaining side effects. It does this well by stating that the call creates a lead and that the team will follow up, which sets expectations that this is not a confirmed booking. Minor omissions remain, such as whether duplicates can occur or how long follow-up takes, but the core behavioral trait is disclosed.

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 with no fluff: purpose and outcome up front, required fields in the middle, and conditional alternative routing at the end. Every sentence adds decision-relevant information for an agent.

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?

For a 9-parameter create action with an output schema, the description gives enough context to invoke it correctly: what the action does, which fields must be present, and what to do in the two most likely error-prone situations. The absence of a return-value explanation is acceptable because an output schema exists.

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%, and the description mostly restates the required parameters rather than adding new semantic meaning. It adds one useful note that organization_id accepts either a slug or an id, but that is already present in the schema, so the description does not exceed the baseline substantially.

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 action ('Submit a booking / staffing request') and a concrete resource ('to a Soundcheck organization'), and clarifies the outcome ('Creates a lead the org's team will follow up on'). It distinguishes this from siblings by calling out the lead-generation nature rather than quoting, sponsorship, or inventory actions.

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 explicitly names alternatives and their triggering conditions: call get_public_org first if organization_id is uncertain, and call analyze_event_to_uef first if the user pasted messy event material. This is clear routing guidance that tells an agent when not to call this tool directly.

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