profile_list

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

The description only says 'List' which implies read-only, but it does not disclose effects of the optional 'session' and 'lease' parameters on the result, nor does it state any permissions, side effects, or observable behavior such as whether it returns a grouped list. With no annotations, the description carries the full burden of behavioral disclosure and is insufficient.

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 a single front-loaded sentence that immediately states the action and result, followed by an alias note. There is no redundant phrasing and every word 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?

The description does not define 'active one' or what the output looks like, and it never references the optional 'session' or 'lease' parameters, the tool has no output schema and no annotations, leaving the agent to infer details from the parameter schemas alone. This is incomplete for a tool that lists all profiles and indicates an active one.

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 schema provides full descriptions for both parameters, so the baseline is 3. The description itself does not mention the parameters, so it adds no extra meaning beyond already structured data; it does not clarify how 'session' or 'lease' would alter the listing output.

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 states the exact action ('List all profiles') and result ('the active one'), and explicitly notes it is an alias of session_list, giving agents confidence in the behavior. This clearly distinguishes it from profile_use, profile_new, and similar siblings.

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?

There is no guidance on when to call this tool instead of session_list or any other listing tool. The alias note hints that they can be used interchangeably, but there is no explanation of scenarios like checking the active profile before using profile_use, so an agent cannot make a justified choice.

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