list_projects

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the 'all projects' scope, which clarifies the operation's breadth, but it does not disclose any additional behavioral traits such as pagination, ordering, or permission requirements. Given the annotation, the bar is lower, and the description is consistent and minimally adequate.

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 wasted words. It conveys the operation and scope efficiently, making it easy for an agent to parse quickly.

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?

Given that there are zero parameters and an output schema exists, the description is nearly complete. The readOnlyHint annotation adds the safety profile. It could mention pagination or sort order, but for a simple list operation, these are not critical gaps.

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 nothing for the description to explain about parameter semantics. The baseline of 4 is appropriate because no parameter documentation is needed.

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 all projects in EasyPanel' states a specific verb and resource, clearly identifying that this tool returns every project. It distinguishes itself from siblings like get_project (single project) and create_project (mutation) because it explicitly targets all projects.

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 usage is implied by the description: call this when you need the full set of projects. However, there is no explicit guidance about when to prefer this over get_project or how it relates to other project-related tools, so it doesn't fully cover usage context.

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