list_admin_websites

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

No annotations are provided, so the description carries the full burden. It discloses the admin-only, self-hosted-only scope and that this is a listing operation, but it omits pagination behavior, auth requirements, and default ordering, which matter for five parameters.

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 filler. Its brevity borders on under-specification, but every word contributes to identifying the tool and its scope.

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 no annotations, five undocumented parameters, no output schema, and many similar list tools in the sibling set, the description is far too thin. It identifies the audience but says nothing about pagination, filtering, sorting, or result shape.

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?

Schema description coverage is 0% and the description mentions none of the five parameters (page, search, orderBy, pageSize, sortDescending). It adds no meaning beyond the bare schema, leaving key filtering, sorting, and pagination semantics entirely undocumented.

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 every website") and adds a meaningful scope qualifier ("self-hosted admin only") that distinguishes it from the sibling list_websites. It does not explicitly name list_websites, but the admin/self-hosted constraint makes the distinction inferable.

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 parenthetical gives a condition for use (self-hosted admin only), which implies when this tool applies rather than list_websites. However, it doesn't name the alternative or state explicitly when not to use it, leaving the agent to infer the boundary.

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