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

No annotations are provided, so the description carries the full behavioral burden. It discloses one useful trait ('Warns on first-index freeze'), but says nothing about the fact that 'rewrite' mutates state, what permissions are needed, what is overwritten, or whether changes are reversible.

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?

It is a single front-loaded sentence with no filler, which is good, but the telegraphic abbreviation style (bare 'serviceName', 'first-index freeze') omits the context needed to make the brevity useful rather than just cryptic.

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?

This is a mutating rewrite tool with no annotations, no output schema, and 0% schema coverage, so the description should do substantial work. Character limits are the only concrete detail; mutation effects, prerequisites, and the buyer_phrases input are all missing.

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%, so the description must compensate. It offers length limits (≤32, ≤500, ≤5) but those map to the unlisted serviceName/description/tags rather than the real parameters, and buyer_phrases is never mentioned, leaving its semantics entirely unexplained.

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?

States a specific verb (Rewrite) and the goal (buyer-query rank), which distinguishes it from read-oriented siblings like oracle_ask and oracle_health. However, the resources it names (serviceName, description, tags) do not match the actual parameters (buyer_phrases, current_description), leaving the agent unsure what is really being rewritten.

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 phrase 'for buyer-query rank' hints at intent but gives no when-to-use guidance, prerequisites, or comparison to alternatives. None of the sibling tools are referenced, so the agent must guess when this applies.

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