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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds substantially beyond that: single-ref scope per call, the mirror namespace it writes into, idempotent upsert behavior on re-import, audit logging, and the returned fields including previousSha. For a write tool with no output schema, this is close to the full behavioral picture an agent needs.

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?

Front-loads the access precondition and the core action, then layers rationale, idempotency, and return shape in short declarative clauses. No filler; every sentence carries either a constraint or a consequence the agent would otherwise have to guess.

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?

Despite having no output schema, the description enumerates the return object keys, and it covers auth, ref scope, mirror destination, and re-import behavior for a 3-parameter mutation tool. Nothing material is missing for a correct invocation.

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%, so the baseline is 3; the description still adds meaning by constraining ref to one tag/branch/full SHA and by showing how `action` (as written in workflows) maps to the mirror path. The upstream_url override is left to the schema, which already documents its default, so this stops short of a 5.

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 (import), a specific resource (a third-party GitHub Action at exactly one ref), and the exact destination (gluecron-actions/<owner>--<repo>). It also explains the downstream effect in workflow terms (`uses: owner/repo@ref`), so the agent can distinguish this from any other mutation sibling without opening a schema.

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?

Gives the prerequisite (site admins only, 'admin'-scoped token), the condition that motivates use (workflow runs never fetch from github.com, so an unimported action is skipped), and the re-import semantics for refreshing an existing ref. That is explicit when-to-use plus the operational consequence of not using it.

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