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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it offers none. It does not state whether the operation is a write, has side effects, requires permissions, is reversible, or what happens on success/failure. The description is entirely silent on behavior.

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 brief ('create task'), which could be seen as concise, but it is under-specification rather than effective brevity. It does not front-load any useful information and fails to justify its presence given the tool's complexity. Every sentence (or word) should add value, and here none does.

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?

For a tool with 29 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what constitutes a task, what the common use case is, how to structure the required 'title' and 'description', or what the system expects in return. An agent cannot reliably call this tool without additional external knowledge.

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 29 parameters with 0% description coverage, and the description 'create task' adds no meaning to any parameter. The agent cannot know the purpose of fields like 'source_expectations', 'relay_leg_minutes', or 'next_action_kind' from the description alone, and the schema lacks descriptions too, leaving the agent completely without guidance.

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 'create task' is a direct restatement of the tool name and provides no additional specificity about what a task is, how it differs from other tools, or what creating one entails. It does not distinguish from siblings like create_room or task_action, and conveys the same information as the name alone.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention scenarios, prerequisites, or constraints, and the sibling tool list (e.g., create_room, post_message) suggests alternative actions that are not compared. The user is left to infer the usage context entirely.

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