dataverse_list_processes

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) are consistent. Description adds significant context: default type=1 to avoid duplicates, exclusion of category 5, and additional OData filter support. No contradiction.

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?

Well-structured with bullet-style explanation of categories and filters. Content is justified but could be trimmed slightly without losing clarity.

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?

Covers all key aspects: default exclusions, parameter usage, filter examples, and output projection. Output schema exists, so return values are documented. Adequate for an agent to select and invoke correctly.

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 high with descriptions. The description adds value by explaining default behaviors (type defaults to 1, category excludes 5) and providing filter examples, going beyond schema details.

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?

Description clearly states it lists classic processes (workflows, business rules, actions, BPFs) from the workflow entity, with specific verb and resource. It distinguishes from siblings like dataverse_get_cloud_flows by explicitly excluding cloud flows unless requested.

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?

Provides when-to-use guidance (list classic processes) and when-not (cloud flows excluded by default). Includes details on category and type filters but lacks explicit mention of alternative tools for specific scenarios.

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