List instances

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that it lists all instances for an environment, but does not disclose pagination, ordering, or potential size of results. It adds marginal context beyond annotations.

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 efficient sentence (12 words) that is front-loaded and to the point. No wasted words, but could briefly mention the optional filters or response format for extra utility.

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?

With no output schema, the description does not specify what the response contains (e.g., list of instance objects with fields). For a simple list tool with good annotations, it is minimally adequate but could be more complete by mentioning pagination or common use cases.

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 parameter schema has 100% description coverage, so each parameter is already documented. The description only reinforces that 'environment' is required for filtering, but does not add new meaning to the optional filter parameters. 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 the tool gets a list of instances for a given environment, specifying the resource and scope. However, it does not explicitly differentiate from sibling list tools like laravel_cloud_list_environments, though the context is clear.

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 need instances for a specific environment, but does not provide explicit guidance on when to use this tool versus alternatives like get_instance or create_instance. No exclusions or alternatives are mentioned.

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