ghl_store_update_shipping_rate

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

Annotations indicate idempotent and not destructive, but the description adds no behavioral context beyond 'update'. It does not describe what happens to fields not included, error cases, or that the operation returns the updated rate or success confirmation. For a mutation tool with no output schema, more detail is expected.

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 brief (2 sentences) but contains a grammatical error ('allows update a shipping rate'). Including the full endpoint path is unnecessary clutter for an AI agent. It could be more polished and front-loaded with essential info.

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 at least mention what the tool returns after a successful update. It also lacks explanation of the nested body properties' purpose as a group. The description is too minimal to give a complete understanding of tool behavior and usage.

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 all parameters. The description repeats the endpoint but does not add meaning to the parameters themselves (e.g., explaining which fields are commonly updated together or constraints). Thus, it provides no additional value beyond 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 that the tool updates a shipping rate, using the verb 'update' and the resource 'shipping rate'. The endpoint path in the description explicitly includes the required IDs, confirming the resource. While it doesn't explicitly contrast with create/get/delete siblings, the name and endpoint pattern make the differentiation obvious.

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 no guidance on when to use this tool versus alternatives. It does not list prerequisites, mention that shipping zone and rate must exist, or explain that this is for modifying an existing rate rather than creating a new one. No exclusions or conditions are given.

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