Show Environmental

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that it returns a JSON object and mentions the GET endpoint, but does not disclose significant new behavioral traits beyond annotations. Adequate but not enhanced.

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 concise (4 sentences, ~70 words) and front-loaded with the main action. Each sentence adds value, but it could be slightly improved by noting optional parameters briefly. No waste.

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?

Given the 5 parameters, no output schema, and good annotations, the description covers the main purpose and required parameters. However, it omits explanation of optional parameters (incident_id, page, per_page) and does not clarify the resource hierarchy (environmental vs incident). Mostly complete.

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% with descriptions for all parameters. The description only lists required parameters without adding extra meaning or clarifying optional ones. Baseline score of 3 is appropriate as description adds no semantic value beyond schema.

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 returns an Environmental record and explains it fetches full details by identifier. It distinguishes from sibling list tools (list_environmentals) but uses 'Incidents' interchangeably, which may cause minor confusion. Overall, purpose is clear.

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 implies usage when you have a specific identifier, but does not explicitly state when to use this tool versus alternatives (e.g., list_environmentals). Required parameters are listed, but no guidance on optional parameters or when not to use.

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