ise_dc_view_profiled_endpoints_summary

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 reporting operation, whether results are paginated beyond the limit parameter, what the default row count behavior is, or what the output format looks like (since there is no output schema).

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 compact paragraph that efficiently communicates the report's purpose and lists the filterable columns. It's reasonably front-loaded with the tool's nature ('[Report] Profiled Endpoints Summary'). No wasted words in describing the purpose.

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 report view, and the filter params are self-describing, which covers much of the operational need. However, with no output schema, no annotations, and no guidance on which columns map to which filter_column values, there's a gap. The column list is useful but doesn't clarify how filter_column relates to those headers or what the report output shape is.

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 has 100% description coverage for all 7 parameters, each with clear descriptions (e.g., limit max, days_back semantics, filter_op enum values, deployment targeting). However, the description adds no additional meaning beyond what the schema already documents; for instance, filter_column doesn't specify which columns are valid filterable values (only listed in the description, not schema).

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 'Profiled Endpoints Summary' report that displays profiling details about endpoints accessing the network. It lists the filterable columns. However, it doesn't distinguish from sibling ise_dc_view_* report tools or clarify what makes this specific report unique versus other views.

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 guidance on when to use this tool vs alternatives. It doesn't say when one would need profiled endpoint data versus registered endpoints (ise_dc_view_registered_endpoints) or other data collection views. The report nature is implied but no exclusions or alternative tool references are given.

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