github_migrations_unlock_repo_for_authenticated_user

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

No annotations are provided, and the description consists solely of 'Unlock a user repository'. It does not disclose any behavioral traits such as required authentication, side effects, or what the unlock operation entails.

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?

While the description is brief (one sentence), it is under-specified and lacks necessary detail. Conciseness should be balanced with completeness; here it sacrifices essential 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?

Given the complexity of GitHub migrations and the lack of annotations or output schema, the description is completely inadequate. It does not explain what unlocking a user repository means in the migration context, nor does it cover any additional behavioral or usage details.

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?

The input schema has 100% description coverage, but the descriptions are just the parameter names ('migration_id', 'repo_name') without additional context. The tool description adds no meaning beyond the schema, failing to explain how these parameters relate to the unlock operation.

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 'Unlock a user repository' which is a clear verb-resource pair. However, it does not specify the context of migrations, making it insufficient to distinguish from other unlock-related tools like github_migrations_unlock_repo_for_org. The purpose is understood but lacks differentiation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when unlocking is appropriate, or any conditions for use.

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