reports_anon_rss_swap_memory_get

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

No annotations are provided, so the description carries the full behavioral burden. 'Get ... metadata' weakly implies a read-only operation, but nothing is said about authentication, rate limits, error behavior, or what 'metric-set metadata' actually contains. It notes the resource path format but little else about behavior.

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, front-loaded with the operation and immediately followed by the path format. No padding or redundancy, though the format hint could be labeled more explicitly as applying to the 'name' argument.

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?

With no output schema and no annotations, the description should explain what metadata is returned and how this differs from the paired _query tool. It gives only the resource path, leaving the return value and the sibling relationship undocumented.

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 single 'name' parameter, so the description must compensate. The 'Format: apps/{packageName}/anonRssAndSwapMemoryUsageMetricSet' hint usefully indicates what 'name' should contain, but it is ambiguous whether the full path or just the package name is expected.

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?

States a specific verb ('Get') and a specific resource ('anonymous RSS + swap memory usage metric-set metadata'), and even names the resource path format. However it never distinguishes itself from the near-identical sibling reports_anon_rss_swap_memory_query, leaving the get-vs-query distinction to inference from the naming convention.

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 use this rather than reports_anon_rss_swap_memory_query (data) or the other reports_*_get metadata tools. The get/query convention is only implied by the tool name, not explained in the description.

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