List configuration profiles

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results carry IDs usable by deploy_config_profile, which is genuine value, but it does not disclose anything about include_deleted behavior or result volume/ordering.

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 with the resource and its purpose front-loaded, a compact parenthetical for examples, and no redundant restatement of the title or annotations.

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 two-parameter read-only list tool with no output schema, the description covers what is returned (profiles plus IDs) and why. The remaining gap is the undocumented include_deleted flag, which is a minor but real omission.

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 coverage is only 50%: the 'os' enum is documented in the schema, but 'include_deleted' has no description anywhere. The description does not compensate — nothing explains that deleted profiles can be included or what the default excludes, leaving one of two parameters semantically opaque.

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 configuration profiles defined in Miradore') and enumerates profile categories (Wi-Fi, restrictions, email). It also names the downstream sibling 'deploy_config_profile', so an agent can tell this apart from list_devices, list_tags, or deploy_config_profile itself without opening a schema.

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 phrase 'for use with deploy_config_profile' gives a clear use context: fetch IDs before deploying a profile. There is no explicit when-not guidance (e.g., not needed if you already know the profile ID), but the intended role is unambiguous.

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