appservice_plan_list

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

No annotations are provided, and the description only states the basic action. It does not disclose any behavioral traits such as permissions needed, side effects, or pagination behavior. For a list operation, this is minimal.

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 very concise, with two sentences plus an argument list. It is front-loaded with the purpose. However, it lacks formal structure like sections or explicit notes, but it is efficient.

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 the tool has an output schema, return values are covered. The description is adequate for a simple list operation, but it omits details like pagination, ordering, or that it returns an array. Slightly incomplete for a production 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?

The input schema provides only type and default without description, so the description adds value by explaining that 'resource_group' is an optional filter. This clarifies the parameter's purpose beyond what schema offers.

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 tool lists App Service plans, specifying the scope as 'in the subscription or resource group'. It uses specific verb 'list' and resource 'App Service plans', distinguishing it from sibling tools like 'appservice_plan_show' which shows a single plan.

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 implies usage by providing an optional filter, but it does not explicitly state when to use this tool versus alternatives such as 'list_resources' or other plan-specific tools. No guidance on when not to use it is given.

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