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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context: org variables require an admin-scoped token, the caller must be a repo/org admin, and pagination defaults (limit ≤100, default 30; offset). That is meaningful disclosure beyond the structured fields.

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?

Four dense sentences, front-loaded with the purpose before routing, pagination, and return shape. Every sentence carries information; slightly compact/run-on but no filler.

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?

With no output schema, the description helpfully specifies the return shape ({scope, total, limit, offset, nextOffset, variables:[...]}), and it covers auth scope, admin requirement, and pagination. Nothing needed to call the tool correctly is missing.

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 combination semantics the schema does not encode (which parameters to pass together for each scope, and that org requires an admin token). It reinforces the limit default/ceiling already present in 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 (List) and resource (Actions configuration variables) and even shows the syntax (${{ vars.NAME }}). It is clearly distinguishable from the singular sibling gluecron_get_variable and from gluecron_list_repo_secrets, which handles a different resource.

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 explicit routing rules: owner+repo for repository scope, owner+repo+environment for environment scope, org for organisation scope, plus the admin prerequisite. It stops short of naming sibling alternatives (e.g. get_variable) or stating when not to use it, so it falls just below the top band.

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