list_asim_content

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

With no annotations, the description carries full burden. It mentions the default return limit (max 100 results) but fails to disclose whether the operation is read-only, requires authentication, or how force_refresh affects results. 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 concise, with two sentences that efficiently convey the tool's purpose and a key behavioral trait. Every phrase is necessary and serves a clear 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?

Given 8 optional parameters, no output schema, and no annotations, the description is incomplete. It lacks explanation of what ASIM content encompasses, the return format, pagination behavior, and the effect of force_refresh. A more comprehensive description is needed for adequate context.

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?

Although schema coverage is stated as 100%, the description only covers three parameters (type, name, path_contains) while ignoring limit, force_refresh, and repository parameters. Additionally, the description claims 'Returns max 100 results by default' but the schema shows default 1000 for limit, creating a contradiction. The description adds minimal value beyond the 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 the verb 'List', the resource 'Microsoft Sentinel ASIM (Advanced Security Information Model) content', and specifies filtering options (type, name, or file path) and a default limit. The tool is distinct from sibling tools that list other types of content (e.g., list_parsers, list_dashboards).

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 is provided on when to use this tool versus alternatives like list_parsers or search_solutions. The description does not include any use cases or exclusions, leaving the agent to infer when this tool is appropriate.

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