particles.report

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

With no annotations, the description must fully convey behavioral traits. It states 'Report live RNA properties' but omits any disclosure about side effects, permissions, or output format. For a report tool, it's likely read-only, but this is not explicitly stated, and the response structure is unclear.

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 of 11 words with no redundancy. It efficiently conveys the core purpose.

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 tool lacks an output schema, and the description does not specify what 'live RNA properties' are included, the format of the report, or error handling. Given the complexity of particle systems, more detail is needed for an agent to correctly use the tool.

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 description adds marginal value over the schema's title fields—'for one or all particle systems' aligns with the 'name' parameter's default. However, schema description coverage is 0%, and the description does not elaborate on parameter formats, constraints, or the required 'object' parameter's role (e.g., is it the object containing particle systems?).

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 reports live RNA properties for one or all particle systems, using a specific verb ('Report') and resource ('live RNA properties for one or all particle systems'). It distinguishes itself from sibling tools like 'particles.systems' which list systems, and 'particles.set' which modifies.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, when not to use it, or any prerequisites. Users are left to infer context from the tool name and siblings.

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