webmaster_manage_reconcile

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

Annotations already declare idempotentHint=true and readOnlyHint=false, so safety traits are covered. The description adds genuinely new behavior beyond the annotations: it resolves state by reading the provider rather than resending the write ('never resends'), which tells the agent the mechanism and that no duplicate mutation will occur.

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?

A single front-loaded sentence with no filler. It is efficient, though so terse that it leaves required information (parameter semantics) unstated.

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?

An output schema exists so return values need no prose, but the 0% parameter coverage and absent usage routing leave the definition incomplete for a three-parameter mutation-adjacent tool. An agent still cannot tell what to pass or precisely when to choose this over the sibling prepare/apply/read tools.

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 0% across three parameters (operation, idempotency_key, args), so the description must carry the burden, yet it says nothing about any of them. The concept of the idempotency_key is only obliquely gestured at by 'never resends'; operation values and args shape are entirely undocumented.

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 states a specific action ('settle an uncertain Webmaster management write by reading the provider') and identifies it as the reconciliation step of a write workflow. However, it does not name the closely related siblings (webmaster_manage_prepare, webmaster_manage_apply, webmaster_manage_read) or distinguish itself from webmaster_reconcile_action, so an agent must infer placement in the workflow.

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?

It implies the trigger condition ('uncertain write') but never states explicitly when to prefer this over prepare/apply/read, nor what constitutes 'uncertain'. The alternative tools exist and are not referenced, so routing depends on inference from the tool name.

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