update_estimated_effort

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

The description mentions only that it updates estimated hours, with no information on side effects, permissions, idempotency, or error behavior. Since annotations are absent, the description alone does not disclose any behavioral traits beyond the basic action.

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 immediately states the purpose and the key constraint. It is appropriately sized, front-loaded with the [Project Management] tag, and contains no redundant or irrelevant information.

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 tool has 8 parameters and no output schema, the description provides minimal context. It does not explain the overall workflow, expected outcomes, or any relation to other tools. The guidance is too sparse to fully understand when and how to use it in a broader context.

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?

All 8 parameters have descriptions in the schema, covering their meanings (e.g., owner, spentTime, organizationId). The tool description adds no extra semantic detail beyond what the schema already provides, so the parameter semantics are adequately covered by the schema.

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 updates registered estimated hours and explicitly distinguishes it from update_work_item by noting the controlled-field constraint. The verb 'update' and resource 'estimated hours' are specific, making the purpose 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 description provides a specific usage hint by warning against using update_work_item.customFieldValues, which guides when to use this tool. However, it lacks comprehensive guidance on alternatives, preconditions, or typical scenarios, so it only partially addresses usage.

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