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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=true, so the safety/replay profile is largely pre-supplied. The description's replay-via-request_key clause adds mechanism, but it does not say what is created, whether the import is synchronous or queued, or what the saved GitHub grant requirement concretely means.

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?

A single front-loaded sentence with no filler. It is efficient but compressed to the point of jargon ('identifies replay'), which costs a little clarity without wasting words.

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?

An output schema exists, so return values need not be described, and all three required params are covered by the schema. However, for a mutating, open-world tool depending on a pre-existing resource grant, the description omits failure behavior (e.g., unauthorized/unselected repository) and whether the import completes immediately or is polled via source_operation_read.

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 100%, and every parameter is already documented there — including request_key as 'identical retries retain this key', which the description merely restates. Baseline 3 applies; no parameter meaning is added beyond the schema.

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?

States a specific verb (Imports) and resource (repository docs), scoped to 'authorized' repos. The repository-vs-drive-vs-website distinction is implied by the noun alone rather than being called out against siblings like source_import_drive or website_import, so differentiation is inferential rather than explicit.

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 when-to-use guidance, no exclusions, and no named alternative among the many sibling import/add/upload tools (source_import_drive, source_add, source_upload, website_import). The only hint is 'authorized', which gestures at a prerequisite without stating it.

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