Deploy configuration profile

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavior beyond that: nothing about idempotency (does redeploying overwrite an existing profile assignment?), what changes on the device, required permissions, or failure modes. For a write operation that alters device state, that is a real gap even with the lower annotation-based bar.

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?

One short sentence, front-loaded with the action and resource, with the provenance hint in parentheses where it belongs. 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?

For a two-parameter mutation with no output schema, the definition is minimally sufficient: an agent knows what to call and what IDs to supply. It is not complete enough to predict the outcome — no statement of what a successful deployment does to the device, whether it replaces a prior profile, or how errors surface.

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 both device_id and profile_id are already documented in the schema, including the 'from list_devices' provenance. The description's '(from list_config_profiles)' is the only added meaning and it mirrors the schema pattern rather than extending it; 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?

The description states a specific verb ('Deploy') plus resource ('configuration profile') and target ('to a device'), so the operation is unambiguous. It also points at the source of the profile via list_config_profiles, which helps separate it from read-only siblings, though it never mentions the closely related deploy_application sibling.

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?

It gives one useful routing hint — get the profile_id from list_config_profiles — which implies 'call that first.' There is no when-not guidance, no prerequisites (e.g., device must be enrolled/active), and no mention of when to prefer deploy_application or remove_config_profile.

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