save_project_workflow_profile

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

No annotations exist, so the description carries the full burden. It does disclose the most important trait: that the operation is a dry-run by default and only writes when confirm=true, which limits accidental mutation. It says nothing about whether an existing profile is overwritten, where 'locally' resolves to, permissions, or reversibility of a write.

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, zero filler, with the preview/write gate front-loaded. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be described, and the confirm gate is the single most important behavior to disclose for a save tool. However, with no annotations and 0% parameter coverage, the description leaves out what 'replace_existing' does to an existing profile and what shape the required profile object takes — meaningful gaps for a mutation tool.

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 0% across 4 parameters, so the description must compensate and largely does not. Only 'confirm' is explained; the required 'profile' object (which is nested and additionalProperties:true), 'project_id', and especially 'replace_existing' are left entirely undefined in both schema and description.

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 concrete verb pair ('preview or save') and a specific resource ('project-bound workflow-profile override') with the scope 'locally'. The dual preview/write nature is clear, though it never names the sibling get_project_workflow_profile, so an agent must infer the read-vs-write split rather than being routed to it.

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 effectively explains the safe default (preview) versus the write path ('Set confirm=true'), which is real usage guidance. It gives no guidance on when to choose this over get_project_workflow_profile or validate_workflow_profile, and no exclusions or prerequisites are stated.

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