github_agent_tasks_create_task

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

No annotations provided, so description must disclose behavior. It only says 'Create a task' without mentioning side effects, required permissions, or what the body object entails. Lacks essential behavioral details.

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?

Under-specified; a single sentence is too minimal for a tool with 3 parameters and no annotations. Fails to provide necessary context while being short.

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 (3 params, nested object, no output schema, no annotations), the description is completely inadequate. It does not explain what a task is, what the body should contain, or what the response will be.

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% but descriptions are minimal (just parameter names). Description adds no additional meaning beyond the schema. The body parameter is described as 'Request body (JSON object)', which is slightly helpful but still vague.

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?

Description 'Create a task' is a verb+resource but very generic, merely restating the tool name 'create_task'. It does not specify what kind of task (e.g., GitHub agent task) or context like repository. Barely above tautology.

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 on when to use this tool vs alternatives like list_tasks or get_task. No prerequisites, such as requiring owner and repo, are mentioned.

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