List Perssua assistants

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

Annotations already cover the read-only and non-open-world nature, so the description does not need to restate those. It adds the useful scoping detail that only the user's configured assistants are listed and that results include name and id, but it stays silent on ordering, pagination, or empty-list 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?

A single, front-loaded sentence that leads with the verb and resource and then explains the purpose. No filler, no repetition of the tool name, and every clause earns its place.

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-argument, read-only list tool, the description provides the essential return fields and the reason to call it. There is no output schema, but 'name and id' gives an agent enough to invoke and interpret the call successfully.

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?

With zero parameters, the schema already carries complete parameter information, so the description does not need to compensate. The mention of returned fields ('name and id') adds relevant context for interpreting the call result.

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?

States a specific verb ('List'), a specific resource ('the user's configured Perssua assistants'), and the key returned fields ('name and id'). This makes it easy to distinguish from the sibling tools, which create or start sessions rather than enumerate existing assistants.

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?

Implies the right usage moment: call this before starting a session so the correct assistant can be selected. It does not explicitly name alternative tools or state when not to use it, so it falls just short of full guidance.

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