ghl_estimate_template_update

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

The description includes endpoint details and OAuth scopes, adding some behavioral context beyond annotations. However, it does not clarify whether updates are partial or full replacements, which is important given the openWorldHint annotation.

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 with three short sentences. It front-loads the purpose but includes technical details (endpoint, version header) that, while informative, may be more than necessary for an AI agent.

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?

Without an output schema, the description should specify what is returned (e.g., the updated template object). It also lacks mention of the requirement that the template must exist. Given the complexity and sibling tools, the description is insufficiently complete.

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 coverage is 100%, so the input schema already documents both parameters thoroughly. The description does not add any additional parameter semantics beyond what is in the schema, meriting the baseline score of 3.

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 it updates an existing estimate template, specifying the verb 'Update' and the resource 'estimate template'. However, it does not explicitly differentiate from the sibling tool ghl_estimate_template_create, which is for creating templates.

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 is provided on when to use this tool versus alternatives like ghl_estimate_template_create. It does not mention prerequisites such as the need for an existing template, nor does it give conditions or exclusions.

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