Delete a pac auth profile

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

With no annotations, the description carries the burden and does provide useful behavioral context: it removes a profile, is limited to the local credential store, and invokes 'pac auth delete' with the active profile. However, it does not warn that deletion is irreversible or explain what happens if the active profile is removed, which would be valuable for a destructive operation.

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?

Two short sentences front-load the primary purpose and the key constraint, then add the underlying command. Every sentence earns its place with no redundancy or 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?

The description is adequate for a straightforward delete operation with a fully described schema. However, there is no output schema and no mention of return values, errors, irreversibility, or whether at least one of name/index is required, leaving some operational ambiguity for the agent.

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 schema already describes all parameters, so the baseline is 3, but the description adds meaning by clarifying that deletion is 'by index or name' and by noting the local credential store scope. This helps an agent understand that name and index are alternative selectors and that the profile parameter interacts with the active profile context.

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 and resource: 'Remove a pac auth profile', and adds the selection mechanism ('by index or name') plus a key scope constraint ('local credential store only'). This clearly distinguishes it from sibling tools like cs_create_auth_profile, cs_list_auth_profiles, and cs_select_auth_profile.

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 when to use this tool: when a pac auth profile needs to be removed. It also gives a meaningful exclusion ('local credential store only'), but it does not explicitly name alternatives or provide contrast with related auth profile tools, leaving some inference to the agent.

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