feegow_create_appointment

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

With no annotations, the description bears full burden. It discloses that the tool writes data ('ESCRITA — altera dados') and requires a write permission flag. But it omits details on side effects, response structure, or error behavior, which are valuable for safe usage.

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 (one line) and front-loaded with purpose. However, the bracket-format metadata and HTTP endpoint inclusion, while informative, add slight noise. Still efficient overall.

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 tool's complexity (nested body with multiple fields) and no output schema, the description should explain return values or confirmations. It does not, leaving the agent uncertain about what the tool returns after creation. This is a notable gap.

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 100%, so the description adds no parameter info beyond what each property's description already provides. The description does not clarify semantics or relationships among parameters.

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 'Cria um novo agendamento' (Creates a new appointment), providing a specific verb and resource. It distinguishes this tool from siblings like feegow_list_appointments, feegow_cancel_appointment, etc., making its purpose unambiguous.

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 implies when to use (to create appointments) and includes a prerequisite (FEEGOW_ALLOW_WRITES=true). However, it lacks explicit guidance on when NOT to use or direct mentions of alternatives, though sibling tools provide context.

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