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

With no annotations, the description carries the full burden and discloses a key behavioral trait: it only registers the request, not publish the business, and mentions the verification step with a person. It does not cover side effects beyond that, but the critical limitation is clearly highlighted.

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 efficiently structured: first sentence defines purpose, second gives usage context, third lists data requirements, and fourth highlights the important caveat. Every sentence adds value with no 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?

The tool has 9 parameters and no schema descriptions, yet the description covers what the tool does, when to use it, what data to collect, and the critical consequence (no publication until verification). An output schema exists, so return values are not needed in the description. It is complete for its purpose.

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 coverage is 0%, so the description compensates by listing all required data (nombre comercial, giro, ciudad, etc.) and provides example values for 'giro' (barbería, estética, salón, spa). It does not explicitly mention the optional 'notas' parameter, but covers most parameters with meaningful context.

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 registers a business request to appear in Aisha and be bookable, with a specific verb ('Registra la solicitud') and resource ('un negocio'). It distinguishes itself from sibling tools focused on reservations and browsing by targeting business owner sign-up.

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?

Explicitly says 'Úsala cuando el dueño de un negocio pida darse de alta' and specifies required data collection steps. It also clarifies an important exclusion: the tool does not publish the business, providing clear when-to-use and what-not-to-expect guidance.

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