config

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

Annotations already indicate this tool is idempotent and not destructive, but the description adds no additional behavioral context such as authentication needs, side effects of specific actions, or rate limits.

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 short but includes a long list of actions and a referral to help. It is adequately sized but could better front-load core information.

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 5 parameters, no param descriptions, and an output schema, the description is highly incomplete. The tool requires significant external documentation (help tool) to be used correctly.

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?

With 0% schema description coverage, the description fails to explain any of the 5 parameters (key, value, remote_type, force). The agent has no information on how to use them.

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 lists many actions but does not concisely state the tool's primary purpose. 'Server config and management' is vague and does not distinguish it from sibling tools like 'config__open_relay'.

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 merely directs the agent to use the help tool for full docs, offering no guidance on when to use this tool versus alternatives or what each action is for.

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