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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; beyond that the description adds two genuinely behavioral facts: a hard security boundary ('Never returns secret values') and a required permission scope. It does not describe pagination or result-size behavior, which is the remaining gap.

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 dense sentences, front-loaded with the returned resources before the secondary facts about IDs and permission. The attribute lists make the middle sentence slightly heavy but every clause carries real 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?

With no output schema, the description does the work of explaining what comes back (services with docs/version; bindings with provider, endpoint, environment, purpose, usability) plus a critical non-disclosure guarantee. Only the paging behavior of result_offset and the shape of large result sets are left unaddressed.

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 carries the full burden. It implies project_id by saying 'linked to a project', but the result_offset parameter is never mentioned and no pagination semantics are given, leaving half the parameters undocumented in both schema and description.

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?

Uses a specific verb ('List') with two clearly named resources (services linked to a project, and their vault bindings) and enumerates the returned attributes. This is distinguishable from siblings like read_project or read_service_change, which do not cover connector/binding linkage.

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 sentence 'Provides the service_id and binding_id used by other tools' tells the agent exactly why to call this first, and 'Requires resources.read' states the permission prerequisite. It stops short of naming an explicit alternative or when-not-to-use case, so it is clear but not complete.

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