List Endpoint Storage and pull profiles

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

Read-only and open-world behavior are already covered by annotations, and the description adds meaningful context beyond them: it explains what endpoint storage is for, that pull profiles copy files at container boot, and that secret keys are never returned. It does not cover pagination or response shape, but the security and domain behavior disclosure is strong.

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 front-loaded with the core purpose and then briefly explains the two resource types, security handling, and related tools. Every sentence contributes useful context without repetition or filler.

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 zero-parameter, read-only list tool with no output schema, the description provides enough domain context about what is listed, the relationship between buckets and pull profiles, and the security constraint around secret keys. An agent can confidently select and invoke it.

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 tool has zero parameters, so there is no parameter semantics to document and the baseline is 4. The description does not need to compensate for missing schema coverage.

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 uses a specific verb, 'List', and precisely defines the two resources returned: Endpoint Storage buckets and the pull profiles under each. It explains the domain concepts well enough that an agent can distinguish this read operation from sibling create/delete/link tools.

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 useful context by explaining that endpoint storage is attached via edgegap_create_app_version / edgegap_update_app_version and pull profiles via edgegap_link_pull_profile, which helps the agent understand where this listing fits. However, it does not explicitly say when to call this tool versus alternatives, nor does it state exclusions such as 'use this before linking' or 'this does not create resources'.

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