agendamento_cadastrar

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

With no annotations, the description carries full burden. It only states the creation action but gives no behavioral traits such as idempotency, permissions needed, side effects, or what happens if data is invalid. The description is insufficient for understanding the tool's behavior beyond the basic 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 extremely concise, consisting of a single short sentence. While brevity is valued, it lacks necessary detail. The structure is appropriate, but the content is under-specified, earning a middle score.

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 complexity (nested object parameter, no output schema, no annotations), the description is severely incomplete. It does not explain what the tool returns, what fields are required in 'dados', or any constraints. The description fails to provide sufficient context for effective use.

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 input schema has one parameter 'dados' with no description (0% coverage). The description adds no meaning about what fields or structure 'dados' should contain. The agent has no guidance on how to populate this parameter, making the tool very hard to use correctly.

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 'Cria novo agendamento' clearly states the action (create a new appointment) and the resource (appointment). It is a specific verb+resource combination, but it does not differentiate from sibling tools like agendamento_alterar or agendamentos_pesquisar. The purpose is clear but lacks sibling distinction.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites, context, or when not to use it. This leaves the agent with no guidance for selection.

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