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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered. The description adds two genuinely useful facts beyond them: values are redacted for secret entries, and the call requires projects:read. It says nothing about pagination behavior despite limit/cursor existing.

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 efficient sentence with the most important constraint (keys, not values) placed first and the permission note trailing. No filler, though the parenthetical is slightly awkward to parse.

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 shapes need not be explained, and the redaction behavior is disclosed. However, for a paginated five-parameter read tool with 40% schema coverage, the description leaves paging and filtering unexplained — an agent cannot form a complete call strategy from it.

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 only 40%, with limit, cursor and search undocumented in the schema, and the description does not compensate for any of them. It only implicitly anchors on 'environment' and never explains paging or search semantics, leaving three of five parameters without meaning.

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?

The description names the resource (an environment's secrets) and its distinguishing behavior: only keys are returned, values are omitted except for plain non-secret entries. An agent can infer this differs from a value-returning get_secret, though the description never explicitly says 'list' or names a sibling.

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 only usage context given is the permission prerequisite 'Requires projects:read', which is an auth requirement rather than when-to-use guidance. Nothing tells the agent when to pick this over search_secrets or get_secret, and there is no when-not-to-use guidance.

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