grokbot_delete_secret

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

The destructiveHint=true annotation signals a mutating operation, but the description adds the critical nuance that the default behavior is a non-destructive preview, not an actual delete. That two-phase semantics is real behavioral context beyond the annotation, though nothing is said about reversibility or downstream effects.

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 with the core action front-loaded and the important safety caveat immediately after. No filler, though the phrasing is terse enough that it borders on underspecified.

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 mutation with no output schema, the description covers the confirm/preview mechanism but leaves the two required parameters and any error or edge-case behavior unexplained. It is minimally workable for an agent that already understands the secret-name convention.

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 only 33%: agent_id and name are undocumented in both schema and description, and the description adds no meaning for those required params. The confirm semantics it hints at are already fully specified in the schema, so the description fails to compensate for the coverage gap.

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 and resource ('Delete a secret'), which cleanly separates it from siblings like grokbot_put_secret and grokbot_list_secrets. It does not explicitly name an alternative, but the verb+resource pair is unambiguous on its own.

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 conveys the key usage rule: without confirm=true the call is preview-only, which is the main decision an agent must make. However, it offers no guidance on when to prefer this over alternatives or on any prerequisites beyond the confirm flag.

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