List addons

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

Annotations already supply readOnlyHint, openWorldHint, and idempotentHint, so the safe read-only behavior is established. The description adds that the list is scoped to a profile and includes the returned fields, which gives the agent extra context beyond the schema and annotations.

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, efficient sentence that front-loads the verb and resource, then adds only the relevant output fields. There is no filler or redundancy.

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?

A simple one-parameter read-only list is adequately specified with the resource scope, output fields, and implied profile. The only missing piece is a declaration of what happens when the profile_id is omitted, but the input schema default and the simplistic nature of the tool keeps this from being a serious 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?

Schema description coverage is 0%, so the description must compensate, but it only mentions 'a profile' without explaining profile_id's meaning, allowed range, or default behavior. The connection to the single parameter is present but implicit, and no additional semantic value is added beyond what the schema already exposes.

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 clearly states the action ('List') and the resource ('addons installed on a profile'), and it enumerates the output fields (url, name, enabled, sort_order). It is easily distinguishable from the sibling nuvio_list_plugins because the resource is named directly.

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 intended use is clear: call this tool when you want the addons on a profile. It doesn't explicitly compare with alternatives like nuvio_list_plugins or nuvio_inspect_addon, but the resource name in the description gives enough contextual grounding without creating confusion.

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