github_migrations_set_lfs_preference

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

No annotations are provided, and the description is too short to disclose any behavioral traits such as side effects, permissions required, or reversibility. The agent cannot understand the impact of using this tool.

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 extremely concise at four words, but this comes at the cost of clarity and completeness. Under-specification reduces its usefulness, so it does not earn the upper range for conciseness.

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 lack of output schema, annotations, and the complexity of migration-related tools, the description is woefully incomplete. It fails to explain what the LFS preference is, what the body should contain, or what the response will be.

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 100% with basic descriptions for owner, repo, and body. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate. The body parameter is described generically as 'Request body (JSON object)', offering no specific guidance.

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 the verb 'Update' and the resource 'Git LFS preference', but does not clarify that this is for a migration import context, making it somewhat vague. The tool name includes 'migrations', which helps, but the description alone is ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like github_migrations_start_import or github_migrations_update_import. The description lacks context about prerequisites or exclusions.

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