config

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

Discloses side effects like large model download (warmup) and OAuth flow (setup_sync), complementing annotations (readOnlyHint=false, destructiveHint=false). Does not mention error states 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?

Well-structured with ACTION GUIDE, informative but not overly verbose. Could be slightly more concise by grouping related 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?

Covers all actions and key parameters; with an output schema present, the lack of return value description is acceptable. Adequate for a config tool with moderate complexity.

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 coverage, description adds meaning by explaining valid actions, required keys for 'set', and example usage, though it could explicitly state that 'key' and 'value' are only used with action='set'.

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 clearly states 'Server config, sync, and setup' and lists specific actions, differentiating from sibling tools that are mostly memory-related.

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 ACTION GUIDE provides explicit conditions for each action (e.g., 'requires sync_enabled=true'), but does not discuss when to avoid using the tool or compare with alternatives beyond the listed actions.

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