Authorize GitHub deployment

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

With annotations already covering read-only, idempotence, and destructiveness, the description adds useful context: the operation requires owner approval, writes a project file, and that file is non-secret. This goes beyond the structured hints without contradricting them.

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?

One sentence, no filler, action first, and the essential artifact named. Every part earns its place.

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?

The description gives the core operation and adds important context about ownership and file secrecy, but it leaves parameter meanings and sibling-tool selection unaddressed. For a five-parameter mutating tool with low schema coverage, this is adequate but clearly incomplete.

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 of five parameters has a schema description, and the description does not explain how repository, ref, slug, path, or environment map to the OIDC binding or the micro.github.json file. Since schema coverage is low, the description needed to fill the semantic gap and does not.

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 uses a concrete action ('Create') on a specific resource ('OIDC binding') and names the output artifact it writes ('micro.github.json'), so an agent can tell this is the setup/authorization action rather than a listing or revocation. It does not explicitly contrast with micro_github_bindings or micro_github_revoke, but the create/write semantics make the purpose reasonably distinct from its siblings.

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 about when to use this tool versus micro_github_bindings or micro_github_revoke, and no mention of prerequisites such as an existing project, repository, or owner-approval flow. The phrase 'owner-approved' implies a requirement but does not say how to confirm or satisfy it.

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