credentials_titles

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

With no annotations, the description must carry the behavioral burden. It discloses that the tool is a read-only listing operation and that it returns aliases/titles rather than full credential information. A zero-parameter listing tool implies no hidden side effects, though error/availability behavior is not elaborated.

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?

One sentence, front-loaded with the action and resource, followed by a purpose clause. There is no filler, repetition of schema content, or unnecessary detail.

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 zero-parameter listing tool with an output schema, the description provides the essential context an agent needs: what is listed and how the result should be used. Nothing required to decide whether and when to invoke the tool is missing.

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?

The tool has zero parameters, so the input schema is fully complete and there is no parameter documentation burden on the description. The description adds semantic value by explaining that the returned titles are meaningful as start_session base_url values.

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 uses a specific verb ('List') and a precise resource ('saved credential titles/aliases'), and immediately states their purpose as start_session base_url values. This clearly differentiates the tool from sibling credentials_list and credentials_check by framing the output as aliases usable for session startup.

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 description gives a clear usage context: call this when you need credential titles/aliases to supply as start_session base_url. It does not explicitly mention when to prefer sibling tools like credentials_list or credentials_check, so it stops short of full when/when-not guidance.

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