List secret files

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint = false, indicating a safe read operation. The description adds the HTTP method and endpoint but no additional behavioral traits like pagination behavior or rate limits. With high annotation coverage, the bar is lower, but no extra context is given.

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, but the first sentence 'List secret files' is redundant with the title. It is front-loaded with the purpose, but could be slightly more concise. Overall, it is efficient with minimal waste.

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?

The tool is a simple list operation with pagination. The description omits details about pagination behavior (cursor/limit usage) and the response format. However, the schema provides links to pagination docs, and the tool's output is likely standard. Adequate but lacks completeness for a fully autonomous agent.

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%, so the schema already documents all three parameters. The description does not add any meaning beyond what the schema provides, so baseline 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 clearly states 'List secret files for the service with the provided ID' and names the API endpoint. It uses a specific verb and resource, and distinguishes from sibling tools like `render_delete_secret_file` and `render_retrieve_secret_file`.

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 indicates when to use the tool (to list secret files for a service) but does not explicitly state when not to use it or mention alternatives among siblings. Some implicit guidance exists, but no clear exclusions.

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