ise_dc_view_registered_endpoints

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. The description frames this as a 'Report' and says it 'Displays' data, implying it's read-only/safe, but it doesn't explicitly confirm non-mutating behavior. It also doesn't disclose whether results are paginated, how large the dataset could be, or performance characteristics. For a zero-annotation tool, more explicit behavioral disclosure would be warranted.

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 enumerating columns, which is compact. However, the column list is somewhat dense and could be considered over-detailed for the description while other important info (usage, return format) is missing. It's reasonably concise but not perfectly front-loaded with the most important purpose statement.

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?

With 100% schema coverage on 7 parameters and no output schema, the description conveys the tool's purpose and data contents reasonably well. However, for a tool that involves an ISE deployment (the deployment parameter) and complex reporting data, it would benefit from disclosing the return structure or clarifying how the view relates to registered endpoint records compared to other endpoint views. It's minimal-viable but not rich.

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 with their descriptions. The description adds the list of filterable columns, which helps map filter_column values, but the description doesn't add meaning beyond what the input schema provides. 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 ('[Report]') that 'Displays all personal devices registered by the employees' and lists the filterable columns. It has a specific verb+resource and describes what data is shown. However, it doesn't explicitly distinguish itself from sibling report tools like ise_dc_view_endpoints_data or ise_dc_view_profiled_endpoints_summary, which could overlap in purpose.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use it over ise_dc_view_endpoints_data or other data-center view tools. There's no indication of exclusions or when not to use it. The only usage hint is indirect via the '[Report]' prefix and column list.

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