list_profiles

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

The annotations already establish that this is a read-only, non-destructive, open-world operation, and the description adds useful behavioral context by listing returned attributes and clarifying site filtering. It does not add permission, rate-limit, or pagination details, but it does more than repeat the annotations.

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 short and front-loaded, first stating what is listed and then focusing on the only parameter. Every sentence adds concrete meaning without bloat.

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 simple one-parameter read-only tool with an output schema and clear annotations, the description is largely complete. It could be slightly stronger by explicitly stating that omitting site lists all saved logins, but an agent can reasonably infer that from "List saved website logins."

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 parameter burden. It explains that site filters to a single site, gives example domains, and warns that a site may have several accounts; the main omitted detail is what happens when site is null or omitted.

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 gives a specific verb and resource: "List saved website logins," and enumerates the key profile attributes. This clearly distinguishes it from sibling profile-mutation tools such as rename_profile and delete_profile.

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 explains that the site parameter narrows results to logins for that site and notes that one site can have several accounts. However, it does not explicitly say when to choose this tool over related siblings like open_session or start_login, so usage guidance is implied rather than fully stated.

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