create_cycle_time_widget

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation and safety profile is covered. The description adds that it targets an existing dashboard and creates a cycle-time chart, but does not disclose permissions, failure behavior, or return values; with annotations present, this is adequate but not rich.

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 two sentences: a front-loaded purpose statement followed by a critical source-priority rule. There is no filler, and every sentence earns its place.

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 15-parameter creation tool with no output schema, the description plus the rich schema and annotations provide enough to invoke it correctly. It covers the purpose and key parameter precedence, though minor gaps remain around return values and permissions.

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 schema already documents each parameter and the baseline is 3. The description adds non-obvious precedence among filterId, query, and filter, which is not stated in the schema and directly affects how issue sources should be supplied.

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 states a specific verb and resource: "Add a 'Cycle time' chart widget to an existing dashboard." It clearly distinguishes this widget-creation tool from sibling tools such as create_dashboard or create_board.

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?

It gives clear context that the dashboard must already exist and provides an explicit precedence rule for issue sources: filterId > query > filter. It does not name alternative tools or when not to use this tool, but the usage context and parameter-selection guidance are actionable.

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