List Nuvio profiles

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds return scope (all profiles, slots 1..6) but does not add behavioral caveats such as ordering, live vs cached data, or whether only enabled profiles are included.

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 sentence front-loads the action and resource, then packs the return fields into a parenthetical. Every word earns its place and there is no filler.

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 zero-parameter, read-only listing tool, this is largely complete: it enumerates exactly what the result covers (slots, name, avatar, flags, PIN lock state). With no output schema, it could additionally state the result shape or value formats, but that is 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 and the schema coverage is complete by construction, so there is nothing for the description to clarify. The zero-parameter baseline applies and no parameter information is missing.

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 ('List'), a specific resource ('profiles'), and enumerates the return content: slot, name, avatar, flags, PIN lock state. It is clearly distinguishable from sibling mutation tools like nuvio_create_profile and nuvio_delete_profile, and from other list_* tools by naming 'profiles' 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?

The description implies its use is to read the full set of profiles, and sibling names make the contrast with create/update/delete obvious. It does not explicitly spell out when-not-to-use or name an alternative tool, but for a zero-parameter list operation the context is clear enough.

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