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

Annotations only declare readOnlyHint and destructiveHint, but the description adds materially important behavior: values are never returned (so an agent must not attempt secret retrieval here) and the call requires admin access plus 'repo' scope. These are exactly the auth and data-exposure facts the annotations cannot convey.

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?

Three tight sentences: purpose and the names-only constraint first, the use case second, prerequisites and return shape last. Nothing is repeated and no sentence could be removed without losing a fact.

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 compensates by spelling out the return shape ({repository, total_count, secrets:[{name, created_at, updated_at}]}), plus permissions and the no-values rule. For a simple two-parameter read tool, an agent has everything needed to call it correctly and interpret the result.

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% and both required parameters (owner, repo) are documented in-schema, so the baseline is 3. The description adds nothing about owner/repo formats or edge cases such as organisation slugs beyond what the schema already says.

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 and resource ('List a repository's workflow secrets') and pins the output scope with 'NAMES ONLY ... values are never returned'. It implicitly distinguishes itself from the loop-secret and set/delete-secret siblings by saying 'repository's', but it never names an alternative explicitly, so differentiation is left slightly to inference.

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 a concrete when-to-use scenario ('check that a secret such as CRON_SECRET exists before a workflow needs it'), which is far more than most list tools offer. It stops short of stating exclusions, e.g. that it is not the way to retrieve values (use it only for existence checks) or how it differs from listing loop secrets.

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