get_parameter_overview

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

Without annotations, the description carries full burden. It discloses that parameter values are never returned, which is a key behavioral trait. However, it omits details like pagination, permissions needed, or potential performance implications for large result sets.

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 sentences, no redundant information. First sentence states functionality and what is not returned, second sentence gives usage guidance. Efficient and front-loaded.

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?

While the tool is simple with no parameters, the description does not specify the output format or structure (e.g., whether it returns a list of objects with name, type, tier). No output schema exists to fill this gap. Also missing details about potential limits or pagination.

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?

No parameters exist in the schema and schema description coverage is 100%. The description implicitly confirms no input is needed, so it adds no confusion. Baseline for 0 parameters is 4.

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?

Description clearly states it returns all SSM Parameter Store parameters with type and tier, and explicitly says parameter values are never returned. Provides a specific use case, but doesn't explicitly distinguish from sibling tools like get_secrets_overview.

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?

Gives explicit use cases ('checking which config parameters exist' and 'verifying parameter types') but lacks guidance on when not to use it or alternative tools for secrets or detailed configurations.

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