delete_profile

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

No annotations are provided, so the description carries the full burden. "Forget" hints at irreversible removal but says nothing about whether deletion is permanent, whether dependent settings (e.g., a default profile pointer) are affected, what errors occur if the name is unknown, or what the response looks like.

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?

It is a single short sentence with no waste, but the brevity comes at the cost of substance; the front-loaded verb is ambiguous rather than informative. Concision here is under-specification rather than efficiency.

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 no annotations, no output schema, and an undocumented parameter, a destructive tool should disclose irreversibility, error behavior, and argument meaning. The description supplies none of that, leaving the agent unable to call it confidently.

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 single parameter "name" has 0% schema description coverage, and the description adds no meaning: it does not state that it is the exact profile name, whether matching is case-sensitive, or what happens on a miss. The one-parameter baseline does not apply because nothing is explained anywhere.

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?

"Forget a print profile" implies removal of a print profile, and the name plus the sibling set (save_profile, list_profiles) make the intended operation inferable. However, the verb is metaphorical rather than a specific operation like "delete", so what actually happens to the profile is left to inference.

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?

There is no guidance on when to delete versus save or set as default, no prerequisites, no mention of what happens if the profile is currently the default, and no reference to any sibling tool. The agent must guess the usage context entirely.

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