list_platforms

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

No annotations are provided, so the description carries the full burden. It does disclose the return content (platform/family names plus parameter names) and, by omission of any arguments, implies a static read-only enumeration, but it never states that it is read-only, whether the list is static or environment-dependent, or what the output shape is.

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 eleven-word sentence with no filler, and the identifying content is front-loaded. The phrasing 'gun families Model Lab can draw' is slightly cryptic but earns its brevity.

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, no-output-schema listing tool the description needs to convey the return values, and it does so at a high level (families and their parameter names). It stops short of describing format, ordering, or how the 'parameter names' relate to describe_params, leaving a modest 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, so the schema has nothing to describe and this dimension is at the baseline 4. Nothing in the description misleads about arguments.

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 decodes the opaque term 'platforms' as 'gun families Model Lab can draw' and states the payload includes their parameter names, which is clearer than the bare name. It does not, however, differentiate itself from siblings such as list_presets or describe_params, so an agent must infer the boundary. Clear but undifferentiated.

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 statement of when to call this versus the other list_* or describe_params tools. The agent gets no condition, prerequisite, or exclusion that would select this tool over its siblings.

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