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

Beyond the read-only annotations, the description discloses important behavior: documentation is returned first up to 20,000 characters, files are returned in a specific order while fitting into 30,000 characters, and `file` can return up to 1,048,576 characters before falling back to a zip. It also explains what data is exposed, including secrets that have no value yet, and what feature reads include, such as newer versions to merge.

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 content is dense and largely front-loaded around what is read, but it is delivered as one very long paragraph with semicolon-separated clauses. Most details earn their place for a complex read tool, but the lack of structure makes it harder to scan than it should be.

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?

There is no output schema, so the description carries the burden of explaining return contents and does so thoroughly: status, features, versions, data, secrets, documentation, tests, files, truncation limits, ordering, and feature merge context. For this tool's complexity, an agent has enough information to invoke it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful parameter context: `feature` switches from version reading to feature reading, `file` returns a single file in full including tests and resources, and demo usage requires a key from `list_demos`. It reinforces the schema rather than merely repeating it.

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 states a specific verb and resource: it reads a lambda's status, open features, recent versions, data, and a selected version or feature with documentation, tests, and files. It clearly distinguishes modes via the `feature` and `file` parameters and mentions `list_demos` for demo keys, so an agent can tell what this tool does versus narrower siblings.

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 gives clear usage context, especially 'Read the documentation and the history before changing what you did not write,' and explains that `feature` reads a feature instead of a version and `file` reads one file. It also notes demo keys come from `list_demos`. It stops short of explicitly saying when to use this tool instead of alternatives like `list_files`, `read_database`, or `read_logs`.

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