panelica_ftp_get_v1_ftp_accounts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds some useful context beyond annotations by specifying the required scope 'ftp:read' and the HTTP GET method, but it does not disclose return shape, pagination, or filtering behavior.

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 short, front-loaded with the core purpose, and includes relevant transport details. 'Read-only' and 'Category: FTP' are slightly redundant given the annotations and tool name, but the overall structure is appropriately compact for such a simple tool.

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 no-parameter, read-only listing tool with strong annotations, the description covers the essential call context: endpoint, category, required scope, and read-only nature. It does not describe the response format, but no output schema exists and the tool's simplicity makes that a minor gap.

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 the schema carries no burden and the description does not need to explain parameter meaning. The baseline of 4 applies because there is nothing for parameter documentation to add.

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 states a specific verb and resource ('List FTP accounts') and includes the HTTP method and path. It is clear this is a collection-listing operation, but it does not explicitly contrast itself with the sibling by-ID tool panelica_ftp_get_v1_ftp_accounts_id, so differentiation is implied rather than stated.

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 gives no explicit guidance on when to use this tool versus alternatives such as the by-ID FTP account getter or listing tools for other resource types. The intended use is only implied by the phrase 'List FTP accounts'; no exclusions or alternative conditions are provided.

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