Add Allowed GitHub Org

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds nothing beyond that - it does not say whether the entry persists across sessions, whether duplicates error or silently succeed (idempotentHint implies the latter), or when the allowlist takes effect. No contradiction with annotations, but minimal added value.

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?

A single short sentence with no filler and the action/scope front-loaded. It is arguably under-specified rather than padded, which is penalized in other dimensions rather than this one.

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?

An output schema exists, so return values need no explanation, and the single parameter is fully documented. However, for a config-mutating tool the description never explains the surrounding context: what the allowed list governs, required permissions, or how it relates to the origin/directory siblings.

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?

Only one parameter with 100% schema description coverage, so the schema already explains 'GitHub organization name to allow.' The description contributes no additional format constraints (case sensitivity, whether 'owner' vs full URL is expected). Baseline 3 applies when the schema does the work.

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 states a specific verb and resource: adding a GitHub organization to an allowlist scoped to skill repos. It is distinguishable from skill-config-remove-allowed-org, though it does not clarify the distinction from the similarly named skill-config-add-allowed-origin (org vs origin), which is the sibling most likely to be confused with it.

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 add an org versus an origin, no prerequisites (e.g., admin/config scope), and no indication of what effect the entry has on skill loading. The agent must infer all of this from the tool name alone.

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