yaaif_platform_list

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It correctly implies a read-only operation via 'List', but does not explicitly state read-only, nor does it mention any side effects, authentication requirements, or rate limits. For a simple list tool, this is adequate but leaves some ambiguity.

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, concise sentence that front-loads the core action ('List builtin and custom YAA\F platform profiles') and provides useful examples. There is no waste or redundancy.

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?

Although the tool is simple, the description does not specify the return format or detail about the profiles (e.g., IDs, names, status). Since there is no output schema, the agent is left without any indication of what the list will contain. Some additional context about the result structure would improve completeness.

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 and the input schema is empty, so schema coverage is trivially 100%. The description does not need to explain any parameters because there are none. This aligns with the baseline of 4 for tools with no parameters.

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 clearly states the tool 'List builtin and custom YAA\F platform profiles' with specific examples (hosted, local-hybrid, local). It uses a specific verb and resource, and it distinguishes itself from sibling tools like yaaif_platform_use and yaaif_platform_export by being a listing operation.

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?

While the purpose is clear, the description does not explicitly state when to use this tool versus alternatives. There is no mention of exclusions or context like 'use this to see available profiles before selecting one'. The usage is implied by the verb 'list' but no explicit guidance is provided.

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