github_save_credentials

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states credentials are saved 'to disk cache' which discloses the persistence mechanism, a useful detail. However, it does not disclose security implications of storing a token to disk, whether re-saving overwrites existing credentials, or whether credentials are encrypted. For a credential-management tool with zero annotation coverage, more disclosure is warranted.

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?

The description is compact and efficient, using a single opening sentence plus a clean args list. Every line earns its place. It front-loads the purpose clearly. No filler or padding, though it could arguably be slightly longer to cover behavioral details.

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 credential-saving tool with an output schema present, the description covers the essential purpose and lists all parameters. However, it omits behavioral context like overwrite semantics, security warnings, and interaction with the github_connect sibling. Given the tool's simplicity and the presence of an output schema, this is adequate but leaves notable gaps around security and caching behavior.

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 description coverage is 0%, so the description must compensate for all four parameters. It lists each parameter with a brief phrase (name, token, API URL, clone protocol), which adds minimal naming context but does add the crucial detail that 'protocol' accepts 'ssh' or 'https'. However, these are near-repeats of the schema titles and lack format hints, validation notes, or default meanings beyond what the schema already provides.

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 clearly states 'Save GitHub credentials to disk cache for future use' with a specific verb (save) and resource (GitHub credentials). It distinguishes this from siblings by the credential-storage purpose, though it doesn't explicitly contrast it with github_connect (which likely establishes an active connection). Overall clear purpose.

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 implies this is the setup step before using other GitHub tools, but there are no explicit when/when-not instructions or mention of alternatives. It does not say to use github_connect vs this, or whether this is a prerequisite for other tools. No exclusions or misdirection, but guidance is implicit rather than explicit.

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