ise_ers_get_networkdevice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state that this is a safe read operation, whether it returns a 404 on missing ID, what fields are returned, or any authentication/permission requirements. For a retrieval tool with zero annotation coverage, this is a notable 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 concise sentence that efficiently states the core purpose. The deployment guide context is handled in the schema rather than repeated. No wasted words, appropriate length 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?

The tool is a simple single-resource getter with no output schema and moderate sibling differentiation. The description is adequate for the primary action but lacks details on error behavior, ID format, and return structure. It's complete enough for basic use but thin for a tool without annotations or output schema.

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 50%, and the description adds value only via the deployment parameter reference (which is documented in the schema itself). The 'id' parameter is documented by name only; the description doesn't clarify its format (e.g., whether it is a UUID, name, or resource ID). Baseline 3 is appropriate given partial schema coverage.

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 'Get a single Network Devices (NADs) object by ID' with a clear verb (get) and resource (Network Devices / NADs). It distinguishes from siblings like ise_ers_list_networkdevice (list) and ise_ers_search_networkdevice (search-by-attribute) via the 'by ID' qualifier, though it doesn't explicitly contrast these.

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?

No explicit when-to-use guidance is given. The description implies use when fetching a single NAD by ID, but doesn't clarify when to prefer this over search/list variants. The deployment param references ise_list_deployments, but no alternative tool is named for the get-by-id use case.

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