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

Annotations already declare destructive=true and readOnly=false, so the bar is lower; the description adds real operational context beyond them: values are encrypted before leaving AskYourStack, no copy is retained, deletion is via remove=true, and a permission requirement is stated. It could still say whether an existing secret is overwritten on set, but the value-add is clear.

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?

Three dense sentences, mode-switching logic front-loaded, and a short illustrative example at the end. Slightly compressed — the permission clause sits mid-sentence rather than standing out — but nothing is wasted.

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 five-parameter, multi-mode mutation tool with no output schema and thin schema descriptions, the definition covers all modes, the permission gate, encryption/no-retention behavior, and deletion path. Remaining ambiguity (return shape, name-only edge case) is minor.

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 20% (just repo), so the description must compensate — and it does, explaining the semantics of name, value, and remove, plus that environment scopes the repository. It's not exhaustive (no guidance on name-without-value, or value/remove interaction), but it covers four of five parameters meaningfully.

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 names a specific resource (GitHub Actions secrets) and spells out its three modes with their triggering conditions: no name = list, name+value = set, remove=true = delete. An agent can distinguish this from gh_actions, gh_repo_settings, or gh_read without opening the schema.

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?

Mode selection is explicit and conditional ('Without name... With name and value...'), and it adds a prerequisite: setting and removing need "change anything" permission. It doesn't name a sibling alternative for the list case (e.g. why not gh_repo), but within the tool the routing is unambiguous.

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