ise_openapi_deployment_node_get

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the operation is a GET (read-only), which is some transparency, but doesn't disclose whether the node must be active/registered, what happens for invalid hostnames, error behavior, or the response format details for a deployment node retrieval.

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 compact single sentence that front-loads the purpose ('Retrieve details of a deployed node') before the endpoint reference. The deployment param guidance is embedded where it belongs (in schema, not bloating the description). Minimal waste, though the GET path is somewhat technical noise for an agent deciding tool selection.

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-hostname tool with 2 params (100% schema coverage) and no output schema, the description is mostly adequate. However, with no annotations and no output schema, the description doesn't explain what node properties are returned, which could matter for an agent deciding whether this tool satisfies a query. The deployment param handling is well-covered but returns are unspecified.

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 schema coverage is 100%, so both parameters have descriptions in the schema. The 'deployment' parameter description is notably rich: it explains the three accepted formats (name, slug, number), includes an example, and even references ise_list_deployments for discovering choices. This exceeds typical schema descriptions and adds genuine decision-relevant value.

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 'Retrieve details of a deployed node' with the specific verb 'Retrieve' and resource 'deployed node', and includes the exact REST endpoint. It distinguishes from the sibling ise_openapi_deployment_node_list which is the list operation, though it doesn't explicitly name that sibling.

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 for getting a single node's details (contrasted with the list tool) but provides no explicit 'when to use vs alternatives' guidance. The endpoint verb 'GET' implies read-only, and the presence of the list sibling weakly signals this is the detail retrieval tool, but no exclusions or alternatives are named.

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