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

No annotations are provided, so the description carries the burden. It discloses that the response includes expiry and instance counts and is evidently a read operation, but says nothing about required credentials, pagination, or rate limits despite the schema implying private-key-based auth.

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?

A single lean sentence with the verb and resource front-loaded and no wasted clauses. It could be marginally tighter but is efficient and well-ordered.

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 read-only listing tool with no output schema, the description states what is returned (expiry and instance counts) and the scoping rule, which is enough for correct invocation. Missing only auth/pagination detail, which is secondary for enumeration.

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 100%, so the schema already documents all four parameters, including that owner defaults to the configured ID. The description adds a marginal restatement of the owner override but no new syntax or format guidance, so baseline 3 applies.

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 ('Lists') and resource ('every app registered by the owner') and notes the return contents (expiry and instance counts). The 'every app' scope implicitly separates it from the singular flux_get_app sibling, though no sibling is named explicitly.

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?

Usage is implied by the 'list every app' framing and the mention of an optional Flux ID scope, so an agent can infer it's for enumeration. However, there is no explicit when-to-use versus flux_get_app or flux_get_app_stats, and no stated prerequisites or exclusions.

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