List Recycled Environmentals

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

Annotations already indicate read-only and non-destructive behavior. The description adds that it returns a paginated JSON array but incorrectly states 'Incidents' instead of 'Environmentals'. This factual error undermines transparency.

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 contains redundant and inaccurate statements (e.g., 'enumerate Incidents'). It could be more concise and focused. The mix-up wastes space and reduces clarity.

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 no output schema, the description should describe return fields or metadata. It only vaguely mentions pagination metadata and incorrectly states the resource type (Incidents vs. Environmentals). Incomplete and misleading.

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 coverage is 100%, so the baseline is 3. The description adds little beyond the schema, only noting required project_id and pagination parameters. No substantial extra meaning.

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 states it returns a list of Recycled Environmentals for a project or incident, which is clear. However, it later refers to 'enumerate Incidents' instead of Environmentals, causing confusion about the actual resource.

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 description mentions using it for paginated overview and filtering, but does not specify when to avoid this tool or provide alternatives. The confusing reference to Incidents further muddles usage guidance.

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