modal_secret_list

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

No annotations are provided, and the description discloses only the basic action. It does not mention whether the operation is read-only, what the output format is, whether there is pagination, or how the 'env' parameter affects the results. The description carries the full burden for behavioral disclosure and fails to provide meaningful context beyond the headline.

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 a single, clear sentence with no unnecessary words. It is front-loaded and very concise, earning its place with minimal overhead.

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?

This is a simple list operation with one optional parameter, but the description does not mention how the 'env' parameter affects the listing or describe the return format. Since there is no output schema, the description could be more complete by clarifying these aspects, but for a basic list tool, it is minimally acceptable.

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 schema fully describes the sole parameter 'env' with the description 'Environment to interact with', so the schema coverage is 100%. The tool description does not add any additional parameter semantics, but the baseline of 3 applies because the structured schema already handles parameter explanation.

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 'List your published secrets' uses a specific verb ('list') and resource ('secrets'), clearly distinguishing it from sibling tools like modal_secret_create and modal_secret_delete. The phrase 'published secrets' adds a specific scope, making the purpose unambiguous.

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?

The description implies usage: when you want to see the secrets you have published. However, it provides no explicit guidance on when to use this tool over alternatives or any context about environment filtering, which is present in the schema but 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.