ise_ers_get_endpoint

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It merely states 'Get' with no detail on what the response contains, whether this is a read-only safe operation, authentication requirements, or pagination/large-response behavior. For a tool with zero annotation coverage, this is a significant transparency gap.

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 sentence, front-loaded with the verb and purpose. Every word earns its place; there is zero waste. This is appropriately concise for a simple GET-by-ID tool.

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 get-by-ID tool without output schema or annotations, the description is very thin. It doesn't mention what object shape is returned, error behavior for missing IDs, or the relationship to the endpoint resource list. Given sibling tools like ise_ers_search_endpoint and ise_ers_list_endpoint exist, more context distinguishing these would help. The deployment param is documented but the core resource semantics are under-specified.

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 description coverage is 50% - the deployment parameter has a rich description, but the required id parameter has none (just type string). The description says 'by ID' but adds no meaning beyond the schema for the id parameter. With moderate coverage and the description providing minimal param guidance, a 3 is the appropriate baseline.

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 'Get a single Endpoints object by ID' is clear about verb+resource (get, single endpoint by ID). However, it doesn't distinguish this from the many sibling ise_ers_get_* tools beyond the obvious resource name, nor does it differentiate from generic ise_ers_get or search variants. It's minimally clear but not differentiated.

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 (use when you have a specific endpoint ID), and the deployment parameter within the schema hints at context. However, there's no explicit guidance on when to use this vs ise_ers_search_endpoint or ise_ers_list_endpoint, nor any exclusions or alternatives mentioned. Usage context is implied but not stated.

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