list_export_profiles

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

No annotations are provided, so the description must carry the burden; 'List' adequately implies a read-only, non-destructive operation. However, it says nothing about whether a live Painter connection is required, what 'available' means when a preset is missing, or how curated profiles are sourced — relevant for a tool whose whole value is cross-app preset availability.

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 front-loaded sentence with no filler; the resource and the notable extra attribute (preset availability) are both stated immediately.

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?

With an output schema present and no parameters, the description needn't explain return values, and it covers the essentials. It falls short only on prerequisites (Painter running/connected) and how the result feeds export_with_profile or plan_profile_export.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not waste space restating an empty schema.

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 ('List') and a specific resource ('curated engine export profiles'), plus an extra attribute (Painter preset availability). It is distinguishable from siblings like list_export_presets and inspect_export_preset by the 'engine profiles' scope, though it never explicitly contrasts with them.

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?

No indication of when to call this versus list_export_presets, inspect_export_preset, plan_profile_export, or export_with_profile, all of which appear in the sibling list. The usage is only inferable from the phrase 'list ... profiles'; no exclusions or prerequisites are given.

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