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

With no annotations present, the description carries the full burden and delivers rich detail: repeated 'set' rotates credentials, bound keys pick up new credentials on next read, credentials are never echoed, list output omits credentials, and remove is refused while bound keys exist. This is exemplary disclosure of side effects and security behavior.

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?

The description is dense, front-loaded with the core purpose, and organized by action, which makes it easy to scan. The trailing fragment 'Record.' is unexplained and slightly undermines an otherwise well-structured definition.

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?

For a multi-action tool with no output schema and no annotations, this covers the critical behavioral context: rotation, read propagation, never echoing credentials, and remove refusal. The main ambiguity is the 'Record.' fragment and only minimal details about what set/remove return, but callers have enough to use it correctly.

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. The description adds meaningful parameter semantics beyond the schema by explaining that calling 'set' with the same name rotates the stored credential and by linking each action to the required parameters (name/kind for set, name for remove).

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 opens with a specific verb and resource: 'Store a credential set once, under a name,' and immediately ties its purpose to bind_source's `source.connection`. The set/list/remove actions further define its scope, making it clearly distinct from sibling tools like bind_source.

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 clearly explains the use case: store credentials once and reference them by name from bind_source. It does not, however, explicitly state when not to use it or compare it with other configuration-oriented siblings like settings, so it lacks explicit exclusions.

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