list_lustre

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

The description is limited to 'List Lustre filesystems the user can access', adding no behavioral context beyond the read-only nature implied by 'list'. With no annotations, the safety profile and return behavior are not disclosed.

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 front-loaded sentence with no redundant words or details, making it highly efficient.

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?

As a simple list tool with two optional filter parameters and no output schema, the description adequately states the operation and scope. It could mention response structure, but the simplicity of listing Lustre filesystems makes it reasonably complete.

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?

Input schema has 100% coverage with descriptions for both 'permission' and 'provisioned' filters, so the baseline is 3. The description does not elaborate on these parameters, leaving schema to carry the semantic detail.

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 the specific verb 'List' with the resource 'Lustre filesystems' and the scope 'the user can access', clearly distinguishing it from sibling tools like list_clusters or list_nfs.

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?

No explicit usage guidance is provided. The description implies usage when one needs to list Lustre filesystems, but it does not mention alternatives or exclusion criteria.

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