Create Quality Profile

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

No annotations are provided, so the description carries full burden. It only states that confirm must be true, which implies an action requiring confirmation, but does not disclose whether the operation is destructive, any side effects, permission needs, or what happens if confirm is false.

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?

The description is extremely short (one sentence), which is concise but under-specified. It sacrifices essential information for brevity, making it ineffective for an AI agent to understand the tool's proper use.

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?

Given the tool's complexity (15 parameters, no schema descriptions, no output schema), the description is severely incomplete. It fails to provide enough context for an agent to invoke the tool correctly, such as what the body should contain or the effect of dryRun.

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?

With 0% schema description coverage and 15 parameters, the description adds no meaning to the parameters. Only confirm is mentioned, and it is already defined in the schema as a const. The description fails to explain critical parameters like app, body, or the required confirm.

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 clearly states 'Create a quality profile,' specifying the verb and resource. However, it does not differentiate from sibling tools like clone_quality_profile or update_quality_profile, leaving ambiguity about what 'create' entails compared to similar operations.

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 provides no guidance on when to use this tool versus alternatives. It only mentions a requirement (confirm=true) but does not explain use cases, prerequisites, or situations where other tools would be more appropriate.

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