set_issue_estimate

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

The description only states the action without disclosing behavioral traits such as whether it overwrites existing estimates, requires specific permissions, or is reversible. The annotation openWorldHint suggests external effects but adds no detail. More transparency is needed, especially given minimal annotations.

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 is front-loaded and contains no unnecessary words. Every word contributes to understanding.

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 simple setter, the description covers the basic function. However, it omits details like whether the estimate replaces existing values, valid ranges, or implications of openWorldHint. Given the presence of an output schema, completeness is adequate but not thorough.

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 description clarifies that the estimate parameter represents story points or hours, adding meaning beyond the schema which only has titles. However, it does not explain how to distinguish between story points and hours, nor does it cover issue_id. With 0% schema description coverage, the description partially compensates.

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 sets an estimate (story points or hours) on an issue, which is specific to the resource. However, it does not explicitly distinguish from sibling tools like update_issue, which might also set estimates, though the name implies specialization.

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?

Usage is implied by the description: use this to set an estimate. No explicit guidance on when not to use or alternatives like update_issue is provided, so it falls to implied usage.

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