github_migrations_get_large_files

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

No annotations are present, so the description carries full responsibility for disclosure. It fails to state whether this is a read-only operation, what permissions are needed, the type of output (list? count?), or any side effects. The description is too minimal to inform an agent about behavioral traits.

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 three words, but it sacrifices critical information. While conciseness is valued, here it results in under-specification. A slightly longer description could provide necessary context without being overly verbose.

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 the migrations domain and the absence of output schema and annotations, the description is incomplete. It does not explain what 'large files' refers to, the response format, or any filtering behavior. Agents would lack sufficient context to use it effectively.

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 two required parameters (owner, repo) with generic descriptions. The description adds no additional meaning beyond the schema. With 100% schema coverage, baseline is 3, and the description does not improve it.

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 'Get large files' indicates a retrieval operation but is vague about scope. The tool name includes 'migrations' which provides context, but it doesn't specify that these are large files within a migration or repository. It differentiates from siblings like 'get_commit_authors' but lacks precision.

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 such as 'get_import_status' or 'list_repos_for_org'. There is no mention of prerequisites, context, or exclusions, making it hard for an agent to decide when to invoke it.

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