advbox_create_task

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It indicates a create operation (implying mutation) but does not mention side effects, reversibility, permissions, return values, or error behavior. This is a significant gap for a mutation tool with no annotation coverage.

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 a single, concise sentence that front-loads the core purpose ('Create a new task/appointment in Advbox') and then lists key requirements. It is efficient and free of unnecessary 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?

Given the tool has 14 parameters, no annotations, and no output schema, the description is too thin. It identifies required fields but does not explain the return value, success/failure behavior, or any nuances about optional parameters. The schema covers parameter semantics, but the overall context for an agent is incomplete.

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 description coverage is 100%, so the baseline is 3. The description lists required fields (creator ID, guests, task type, lawsuit, start date) which map directly to schema properties, but it adds no additional semantic meaning beyond what the schema already provides.

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 creates a new task/appointment in Advbox, using a specific verb and resource. It distinguishes from sibling creation tools like advbox_create_movement, advbox_create_customer, and advbox_create_lawsuit by explicitly naming the entity type.

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 usage context by listing required fields, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The use case is reasonably clear from the tool name and description, but no explicit guidance is given.

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