check_task_creation

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context by mentioning 'assess its quality,' hinting that it does more than a simple existence check, but it does not explain what quality means or how it is evaluated. No contradiction with annotations exists.

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 for the tool's purpose followed by a structured parameter list. No fluff or repetition. The front-loaded purpose sentence immediately gives the agent the tool's primary function, and the parameter explanations are compact.

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?

With an output schema present, the description need not detail return values. However, it lacks guidance on when this tool should be invoked relative to sibling verification/lookup tools, and it does not clarify what 'assess its quality' entails (e.g., criteria used). Adequate for basic invocation but leaves some contextual ambiguity.

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 0% description coverage for its 5 parameters, but the description compensates by explaining each parameter's meaning, including defaults and optionality. For example, it specifies that created_since accepts durations or dates with a default of '7d'. This is clear and actionable, though some format constraints (e.g., exact date syntax) could be more explicit.

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 uses a specific verb ('Check') and resource ('task matching keywords') and adds the action 'assess its quality,' which clearly indicates what the tool does. It does not explicitly contrast with sibling tools like search_issues, so it lacks full differentiation, but the core purpose is 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 phrasing 'Check if a task matching keywords was created' implies this tool is used for post-creation verification, but it never states when to prefer it over alternative lookup tools such as get_issue or search_issues. Usage context is only implicit, with no explicit exclusions or alternative routing.

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