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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond by disclosing the admin-token requirement, the one-ref-per-import constraint, that re-importing a ref updates it to current upstream state, that the operation is audit-logged, and the skip behavior for unimported actions.

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-loaded with the admin-only requirement, then purpose, then behavioral facts, with zero filler. Dense but every clause (skip semantics, idempotent re-import, audit log, return shape) carries actionable 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?

Covers the auth prerequisite, the mutation/idempotency profile matching the annotations, the operational consequence for workflows, and an inline enumeration of the response fields in the absence of an output schema. An agent has everything needed to call it correctly.

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, but the description adds real meaning: the mirror namespace is derived as gluecron-actions/<owner>--<repo>, only ONE tag/branch/full SHA may be imported per call, and it enumerates the returned fields despite no output 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 (import) and resource (a third-party GitHub Action at one ref) and names the exact target namespace (gluecron-actions/<owner>--<repo>). No sibling tool performs this function, and the description makes that unambiguous.

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 'when' is clear: needed so workflows writing `uses: owner/repo@ref` can run, because workflow runs never fetch from github.com and unimported actions are skipped. It also states the admin-scoped-token prerequisite. It does not name an alternative tool, but no close sibling exists.

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