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

With no annotations, the description carries the full burden and does disclose the key behavioral consequence: jobs on that key stop working immediately. That is the critical destructive-effect disclosure. It omits whether deletion is reversible, whether confirmation is required, and behavior when the name does not exist.

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-loaded with the access gate, then the action, then the consequence. No filler and every clause earns its place.

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?

For a destructive single-parameter tool with no annotations and no output schema, the description covers permission requirements and immediate impact. It lacks reversibility/confirmation details and error behavior, which are the remaining gaps for a delete operation.

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% and the single 'name' property is undocumented in the schema, so the description must compensate. 'Delete a saved provider key by name' clarifies that the parameter is the provider key's name, which is enough for a one-parameter tool, though it does not specify format or case-sensitivity.

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 specific verb (delete) and resource (a saved provider key) with the lookup key (by name) and the gating scope (Pro, owner only). It is trivially distinguishable from its counterpart save_provider_key and from list_providers.

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?

Gives clear preconditions for use – requires Pro tier and owner role – which tells the agent when this call is even permitted. It does not name alternatives or an explicit when-not-to-use (e.g., use save_provider_key to overwrite instead), so it stops short of full routing guidance.

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