ise_ers_search_profilerprofile

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, what filter syntax is expected, whether pagination is applied, or what the response contains. For a search tool that presumably queries ERS, the behavioral context is thin.

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 single sentence is concise and waste-free (no filler), but it's arguably under-specified rather than appropriately concise. It gets credit for being short and front-loaded with the purpose, but doesn't earn bonus for structure since there's very little content.

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 5 parameters, 80% undocumented in schema, no annotations, and no output schema, the description should compensate significantly. It does not. It doesn't explain filter syntax, pagination defaults, or how this differs from the list and generic search variants that exist as siblings. The description is insufficient for an agent to safely and correctly use this tool.

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 only 20%, meaning 4 of 5 parameters lack descriptions. The description only mentions 'ERS filter expressions' without explaining the filter syntax, and does nothing to clarify page, size, sort, or filter semantics. Only the deployment parameter is documented in the schema. The description adds minimal value over the sparse 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 'Search/filter Profiler Profiles with ERS filter expressions' uses a clear verb (search/filter) and resource (Profiler Profiles), but doesn't distinguish from the many sibling search_* tools (e.g., ise_ers_search_downloadableacl, ise_ers_search_guesttype) beyond the resource name itself. The meaning is clear but there's no differentiation beyond the resource type, which is expected given the naming pattern.

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 gives no guidance on when to use this tool versus ise_ers_list_profilerprofile, ise_ers_get_profilerprofile, or the generic ise_ers_search. It doesn't clarify whether this replaces listing or complements the generic search tool. No exclusions, prerequisites, or when-not-to-use guidance is provided.

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