get_lambda_overview

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

With no annotations, the description carries the full burden. It discloses important behaviors: environment variable values are never returned, recentThrottles/recentErrors are CloudWatch counts, and costSignal is a config-level heuristic with no billing API. However, it does not mention that data may be stale (no AWS re-read), which is only covered in the parameter description.

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 four sentences and front-loaded with the return contents. Each sentence carries distinct information (return content, usage, conditional signals, cost heuristic). While longer than minimal, the detail is necessary for the tool's complexity.

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 tool with no output schema, the description explains the returned fields, conditionality (runtime signals), and the costSignal heuristic. It also covers use cases and an alternative. The only gap is the data-freshness behavior, which is explained in the parameter description.

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% for maxAgeSeconds, including advisories, dataHealth reporting, and freshness behavior. The tool description does not mention the parameter directly, but the schema fully explains it, so the baseline of 3 is appropriate.

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 begins with 'Returns all Lambda functions with runtime, memory (MB), timeout (sec), environment variable key names (values never returned), and event source triggers with the correct handler event shape for each,' which clearly states a specific verb and resource. It also differentiates from sibling analyze_function by mentioning 'without running analyze_function'.

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?

Explicitly states when to use: 'Call this when auditing Lambda configuration for default memory (128 MB) or high timeouts, or when you need the trigger event shape for a specific function without running analyze_function.' This names specific use cases and an alternative tool, providing clear guidance.

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