webapp_list

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

With no annotations, the description carries full burden for behavioral disclosure. It does not state that the tool is read-only, idempotent, or any auth/rate limit requirements. The description only says 'list' but does not elaborate on potential side effects or safety.

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 brief and to the point, with a structured 'Args:' section. It wastes no words, but could benefit from a slightly more explicit structure (e.g., stating return value or scope).

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?

Despite having an output schema, the description is too minimal. It does not specify the scope (subscription level or all subscriptions), preconditions, or how it differs from sibling webapp tools. For a simple listing tool, more context is needed to guide proper usage.

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 description adds meaning to the 'resource_group' parameter beyond the schema (optional filter), which is helpful. However, schema coverage is 0% and only one parameter is present. The description could clarify default behavior when the parameter is omitted (e.g., lists all in subscription).

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 action ('List') and the resource ('web apps'), and mentions optional filtering by resource group. It is specific enough to differentiate from unrelated tools, but could be more explicit about the scope (current subscription) to avoid ambiguity with sibling listing tools.

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 (e.g., webapp_show for a single app, list_resources for all resources). There is no mention of context or preconditions for invocation.

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