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

Goes well past the annotations, which only flag destructive and idempotent. The description discloses the concrete idempotent response semantics (deleted:false, already_deleted:true), the downstream effect on workflows, required permissions (admin + 'repo' scope), and audit logging limited to the name.

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?

Front-loads the action and target, then layers idempotency, side effects, permissions, and return shape in compact clauses. No filler or restatement of the schema, and each sentence carries distinct 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?

Despite no output schema, the description summarises the return object ({repository, name, deleted, already_deleted, at}) and covers permissions, audit behaviour, and downstream impact. Nothing an agent needs to call this destructive tool correctly is missing.

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 100% and defines owner/repo/name adequately, so the baseline is 3. The description adds real meaning beyond the schema by explaining how the name value is normalised (cron_secret read as CRON_SECRET), which affects what callers should pass.

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 with scope: 'Delete one workflow secret from a repository by name'. It is immediately distinguishable from siblings list_repo_secrets and set_repo_secret, and even clarifies the name-normalisation rule (cron_secret -> CRON_SECRET).

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 operational context: retries are safe because deletion is idempotent, and workflows referencing the secret stop receiving it. It does not explicitly name alternative tools (set_repo_secret, list_repo_secrets) or state exclusions, so it stops short of the when/when-not/alternatives bar.

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