feegow_reschedule_appointment

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

No annotations are provided, so the description carries full burden. It mentions it's a write operation and gives the HTTP endpoint, but fails to disclose side effects, prerequisites (e.g., existing appointment), or what happens to the original appointment.

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?

Extremely concise: one line with useful tags (write indicator, environment variable, endpoint). No wasted words.

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?

Lacks completeness for a mutation tool: no output schema, no error conditions, no return value description. The agent lacks context on success/failure signals and side effects.

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% with all parameters described. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 verb 'remarca' (reschedule) and resource 'agendamento' (appointment), specifying it changes date/time. This distinguishes it from siblings like create, cancel, or update status.

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?

Includes the requirement FEEGOW_ALLOW_WRITES=true and explicitly marks it as a write operation. However, it does not explicitly contrast with alternative tools for modifying appointments, though the purpose implies rescheduling.

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