list_logic_apps

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

Lacks annotations, so description bears full burden. It mentions that both SKUs are returned and gives workflow count distinction, but does not disclose authentication needs, pagination, or response format. Adequate but not exhaustive.

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?

Three sentences, front-loaded with main action and scope. Every sentence provides useful information without redundancy.

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 no output schema and many sibling tools, the description adequately explains what the tool does and how it relates to others. Could mention response structure or pagination, but is otherwise complete.

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 covers all parameters (100% coverage), but description adds value by explaining the implication of SKU parameter (single vs multiple workflows) and the optional resource group filter.

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?

Clearly states 'List all Logic Apps', specifies scope (subscription/resource group), and distinguishes between Consumption and Standard SKUs. It also directs to sibling tool list_workflows for Standard Logic App workflows.

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 clear context for usage and directs to list_workflows for Standard Logic Apps' workflows. No explicit when-not usage, but the sibling list and description imply when to use alternatives.

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