ise_dc_view_network_devices

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 whether this is a read-only operation, whether it requires specific deployment context, whether results are paginated by default, or what the output format is (columns, rows). There's no reference to the deployment parameter behavior that could affect results. For a query-style report tool with no annotations, more behavioral context is needed.

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 efficient sentence with a useful list of filterable columns. It's front-loaded with the purpose and avoids unnecessary prose. Could be slightly more structured but is appropriately compact for a report 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 report/read tool with 100% schema coverage and no output schema, the description covers the core purpose and filter columns. However, it doesn't explain the relationship to deployments (the deployment parameter exists but no guidance on when it matters), nor does it clarify expected output shape. Given the tool's complexity (7 parameters, deployment targeting), a bit more context about result format would improve completeness.

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 100%, so the schema already documents all 7 parameters well. The description adds value by listing the filterable columns (ID, NAME, IP_MASK, PROFILE_NAME, LOCATION, TYPE) which correspond to filter_column choices. However, the description doesn't add meaning beyond the schema for parameters like limit, order_by, days_back — the schema descriptions cover those. Baseline 3 is appropriate since the schema does the heavy lifting.

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 this is a report tool that gives network device information configured in ISE, and lists the filterable columns. The verb 'Gives' with the resource 'network device information' is clear, and the implicit reference to 'network devices' differentiates it reasonably from siblings. However, it could be more explicit that this returns a list/report of devices and how it differs from ise_dc_view or ise_ers_list_networkdevice.

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 it's a reporting/view tool for network device inventory, which fits with the ise_dc_view_* family naming. It lists filterable columns which gives some usage context. However, it doesn't explicitly say when to use this vs alternatives like ise_ers_list_networkdevice or ise_ers_get_networkdevice (which also relate to network devices), nor does it mention exclusions 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.