wa_phone_retrieve_commerce_settings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read operation, but the description doesn't disclose any behavioral traits such as authentication requirements, rate limits, error conditions, or what format the commerce settings are returned in. This is inadequate for a tool with zero annotation coverage.

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 extremely concise at just two words, with no wasted language. While this conciseness comes at the cost of completeness, from a pure structure perspective, every word serves a purpose and there's no unnecessary verbiage.

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 that this is a retrieval tool with 2 required parameters, 0% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what commerce settings are, what the parameters mean, what format results are returned in, or how this differs from similar tools. The description fails to provide the necessary context for effective tool use.

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 schema has 0% description coverage for both parameters (wabaId and phoneNumber), and the tool description provides absolutely no information about what these parameters mean, their format, or how they should be used. With two required parameters and no schema descriptions, the description fails to compensate for this documentation gap.

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 'Retrieve commerce settings' is a tautology that essentially restates the tool name 'wa_phone_retrieve_commerce_settings'. While it identifies the action ('retrieve') and resource ('commerce settings'), it doesn't provide any specific context about what commerce settings are or how this differs from similar tools like 'wa_phone_retrieve' or 'wa_phone_retrieve_profile'.

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. With sibling tools like 'wa_phone_retrieve', 'wa_phone_retrieve_profile', and 'wa_phone_update_commerce_settings', there's no indication of when this specific commerce settings retrieval is appropriate versus general phone retrieval or profile retrieval tools.

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