config_data

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuine behavioral nuance — that fetch_docs downloads the docs reference only when it isn't kept locally — but says nothing about what refresh or refresh_docs do or what the call returns.

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?

Two short sentences with no filler, and the primary purpose is front-loaded ahead of the parameter note. The RST-style double backticks are noisy but do not cost much space.

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?

For a three-parameter tool with zero schema documentation and no output schema, the description explains only one parameter and never states what the tool returns. An agent cannot confidently decide between refresh and refresh_docs from this text.

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 carry all three boolean parameters. It explains fetch_docs partially (downloads the docs reference when not local) but leaves refresh and refresh_docs entirely undefined, including what is being refreshed and whether they interact.

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 names a resource ("all engine variables for the Config view") but supplies no verb, so the agent must infer from readOnlyHint that this retrieves rather than mutates. "Config view" is also ambiguous relative to siblings like cluster_config or app_page, and no differentiation is offered.

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?

There is no statement of when to call this tool versus cluster_config, app_page, or the other config-adjacent siblings. The only conditional guidance concerns the fetch_docs parameter, not the tool's place among alternatives.

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