Take Metric Snapshot

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds the 'without analysis' qualifier, but does not disclose where metrics are saved, whether a snapshot ID is returned, or any rate limiting. With annotations present, the added context is limited.

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 a single, concise sentence that is front-loaded with the core action. It is well-structured and avoids redundancy, though it omits important details that could be included without harming conciseness.

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?

The tool has an output schema, so return values are covered. However, the description lacks detail about the SSH connection required, the 'save' destination, and when to pick this over record_baseline or analyze_server_snapshot. Given the complexity of the connection parameter, the description is incomplete.

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% for the top-level parameter 'connection'. The description does not mention the parameter or explain how to construct the connection object. While the schema provides nested field descriptions, the tool description adds no value beyond the schema, so the agent gets minimal guidance.

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 the tool's function: 'Collect and save current server metrics'. The verb 'collect and save' is specific, and the phrase 'without analysis' differentiates it from sibling tools like analyze_server_snapshot.

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 implies usage for raw metric collection without analysis, but does not explicitly state when to use this tool versus alternatives. No exclusions or explicit alternative tool references are provided.

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