get_parameter_overview

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

The description discloses a key behavior: 'Parameter values are never returned,' which clarifies output boundaries. However, it does not mention that data may be cached or not re-read from AWS; this is only found in the maxAgeSeconds parameter description, not the main description. Given no annotations, there is a burden on the description to disclose such traits, so this is a notable gap.

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 two sentences that front-load the core purpose and immediately add a usage directive. No filler or redundant information; every sentence contributes value.

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 simple overview tool with one optional parameter and no output schema, the description explains what is returned (all parameters, types, tiers) and what is not (values). The parameter schema covers freshness semantics. It could be more complete about the return format, but the tool is straightforward and the provided details are sufficient.

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?

The input schema has 100% description coverage for maxAgeSeconds, so the schema fully explains the parameter. The tool description adds no parameter-specific meaning beyond what the schema already provides, matching the baseline for full 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 tool returns all SSM Parameter Store parameters with type and tier, using a specific verb ('Returns') and resource ('SSM Parameter Store parameters'). It distinguishes itself from sibling tools like get_secrets_overview by focusing on parameter store metadata.

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?

It explicitly says 'Call this when checking which config parameters exist for a service or verifying parameter types,' giving clear use cases. It does not explicitly state when not to use it or mention alternatives, but the focused purpose makes usage clear enough.

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