list_profiles

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

No annotations are provided, so the description carries the behavioral burden. 'List' strongly implies a non-mutating read, and the enumerated return fields describe the payload, but it never states read-only safety, pagination behavior, or whether the profile set is static or session-dependent. Adequate but not rich for a zero-annotation tool.

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 with no filler. The verb and resource come first, with the launch context and returned fields following in a tight parenthetical.

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?

With an output schema present, the description needn't explain return values, and it still names the key fields. For a zero-argument listing tool under a session-launch workflow, the definition is essentially complete; only the absence of any stated relationship to get_profile_details leaves a small gap.

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 takes zero parameters (100% schema coverage of nothing), so there is nothing for the description to disambiguate and the baseline is 4. The parenthetical field list describes the output rather than inputs, so it adds no parameter meaning but no gap either.

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) and resource (agent profiles) with additional scope detail: the profiles a session can be launched with, plus the fields returned. It implicitly distinguishes from the singular get_profile_details via plurality and the launch-oriented framing, but never names that sibling to make the contrast explicit.

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 phrase 'a session can be launched with' implies this is the discovery step before launch_session, which is useful implied guidance. However, there is no explicit when-to-use statement or routing against get_profile_details, so the agent must infer the choice from the tool names alone.

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