list_apps

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context beyond annotations: admin privileges are required, app_filter changes scope, and pagination behavior is described. It also details the exact return shape, which is not visible in the provided schema.

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 compact and front-loaded with the core purpose, followed by clear parameter and return sections. Every sentence provides needed information, with no filler or repetition of schema defaults.

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 simple paginated list tool with annotations covering safety, this description is complete: it covers authorization, parameter semantics, defaults, pagination, and return structure. An agent has everything needed to call it correctly without inspecting sibling tools or output schemas.

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%, so the description carries the full burden, and it fully compensates. Each parameter is explained with allowed values, defaults, and ranges (app_filter options, limit 1-500, offset). This adds meaning far beyond the bare schema property definitions.

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?

States a specific verb and resource: 'List installed Nextcloud apps.' The admin-privileges note and the return description make the function's purpose unambiguous. It is clearly distinct from sibling tools like enable_app, disable_app, and get_app_info.

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 clearly indicates this is a read-only enumeration tool and notes the admin privilege prerequisite. It does not explicitly name when to avoid this tool in favor of siblings like get_app_info, but the context is sufficiently clear for an agent to choose it appropriately.

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