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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a genuinely important behavioral guarantee beyond them: only names and usage are returned, never secret values, and per-binding access must be requested separately. It does not disclose pagination behavior despite a result_offset parameter.

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 dense sentence with the core purpose front-loaded and no filler. The trailing clause about secrets.use/secrets.export is compact but borders on cryptic in its shorthand notation.

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?

There is no output schema, so the description usefully sketches the return shape (names, usage, binding_id). However, for a two-parameter tool with zero schema documentation, it omits what result_offset does and how paging works, leaving an agent unable to use the full signature confidently.

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 0%, so the description must carry parameter meaning and largely does not. 'Of this project' implies project_id selects the project, but its format and constraints are unstated, and result_offset is never mentioned at all. The binding_id reference describes returned data, not an input, so it does not compensate for the gap.

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 a specific verb and resource ('List the vault references of this project') and gives a concrete example of the identifier format (vault://brevo/key), plus the scope of what is returned (names and usage). It is clearly separable from sibling tools like read_resources, use_secret, and list_access_requests.

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?

It explicitly routes value-retrieval to other operations ('request secrets.use or secrets.export per binding_id'), which tells an agent this tool is for discovery only. The guidance uses dotted operation names rather than the actual sibling tool names (use_secret / export_secret), so the routing is slightly indirect, and no explicit 'when not to use' case is stated.

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