maideo

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: the 72h bookingToken validity, 48h hold before worker dispatch as anti-fraud protection, and the return values (bookingToken and bookingId). It doesn't cover rate limits or error conditions, but provides substantial operational context.

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 perfectly front-loaded with the core action and prerequisites, followed by return values and behavioral details. Every sentence earns its place with zero waste, making it highly efficient for an agent to parse.

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 complex booking creation tool with 9 parameters, no annotations, and no output schema, the description does remarkably well by explaining prerequisites, return values, and key behavioral constraints. The main gap is lack of error handling or edge case information, but it covers the essential workflow comprehensively.

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?

With only 22% schema description coverage, the description compensates well by explaining the purpose of quoteToken (from get_quote) and clarifying that client includes identity, address includes location, and agentConsent represents explicit consent. It doesn't detail all 9 parameters but adds meaningful context for the most critical ones.

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 specific action ('Create a booking') and distinguishes it from siblings by mentioning the required quoteToken from get_quote. It provides a complete picture of what the tool does beyond just the verb.

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 states prerequisites ('Requires a quoteToken from get_quote plus the end-user's identity, address, and explicit consent'), providing clear context for when to use this tool. However, it doesn't mention when NOT to use it or explicitly compare it to alternatives like enroll_avance_immediate.

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