ise_ers_resources

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

No annotations are provided, so the description carries the burden. It states the read-only nature (lists resources) clearly. It doesn't disclose whether this contacts the live deployment, whether it requires auth, or whether it's cached. For a read-only listing tool, this is modest but acceptable context.

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?

Single sentence, zero waste, front-loaded with the core verb and purpose. Every word earns its place.

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 simple enumeration tool with one optional parameter and no output schema, the description adequately covers what happens. It could mention whether output varies by deployment, but the tool is simple enough that this level of detail is largely 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% and the single 'deployment' parameter is well documented in the schema itself, including format options and reference to ise_list_deployments. The description adds no additional parameter detail but the schema is self-sufficient, so the baseline 3 with good schema justifies a 4.

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 lists ERS resources with API paths and supported operations. It uses specific verb 'list' + resource 'ERS resources'. While it distinguishes from per-resource tools like ise_ers_list_endpoint, it doesn't explicitly contrast with ise_ers_list or other sibling generic tools like ise_route/capabilities.

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 this is a discovery/enumeration tool for understanding what ERS resources exist before calling resource-specific tools. However, it doesn't explicitly state when to use this versus alternatives like ise_ers_list, ise_route, or ise_capabilities, nor does it mention it as a prerequisite step.

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