streamdeck_manage_profile

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

No annotations are present, so the description alone must disclose behavior. It only lists mutating actions and does not explain side effects such as whether deletion is permanent, what duplication copies, or whether renaming requires an existing ID. This is a significant gap for a CRUD tool.

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 states the resource and the four actions without wasted words. The structure makes the tool's purpose instantly scannable.

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 four operation modes, five parameters, and no annotations or output schema, the description is too thin. It does not clarify how action selects which parameters are required, nor the relationship between profile_id, profile_name, and new_name, leaving an agent to guess for reanme/delete/duplicate calls.

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% and the schema already documents each parameter's purpose (e.g., new_name for create/rename/duplicate). The description adds no extra meaning, but also does not need to because the schema is sufficient; 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 names the resource (Stream Deck profiles) and enumerates the supported operations: create, rename, delete, or duplicate. This clearly sets it apart from sibling tools like streamdeck_read_profiles or streamdeck_write_page. However, the verb 'manage' is generic and no explicit contrast with siblings is provided.

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 operation list implies when to use the tool (whenever a profile needs to be created, reanmed, detected, or dupliced), but there is no explicit guidance about prerequisites or when to prefer sibling read/write tools. Usage must be inferred rather than stated.

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