GetMemUsedData

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While '获取' (get) implies a read operation, it doesn't specify authentication requirements, rate limits, data freshness, or what format/units the memory usage data is returned in. This is inadequate for a metric retrieval tool.

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, efficient Chinese phrase that directly states the tool's purpose without any unnecessary words. It's appropriately sized for what it communicates.

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 metric retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of memory usage data is returned (percentage, MB/GB, time series), the time range covered, or how to interpret the results. The agent would struggle to use this tool effectively.

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 100%, so the schema already documents both parameters (InstanceIds and RegionId) adequately. The description adds no additional parameter information beyond what's in the schema, which is acceptable given the high schema coverage.

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 action ('获取' meaning 'get') and resource ('内存使用量指标数据' meaning 'memory usage metric data'), making the purpose understandable. However, it doesn't differentiate from sibling tools like GetMemUsageData, which appears to be a similar memory-related metric tool.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like GetMemUsageData, GetCpuUsageData, and GetDiskUsageData, there's no indication of how this memory usage tool differs from GetMemUsageData specifically.

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