webapp_view_logs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'View', implying a read-only operation, but fails to disclose any side effects, required permissions, rate limits, or details about what logs are included or excluded.

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 short and front-loaded with the purpose. However, the parameter listing is redundant with the input schema and could be more efficient by omitting the list entirely if the schema is sufficient.

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 that an output schema exists, the description does not need to explain return values. However, it lacks context about the log scope, filtering capabilities, or data volume. It is minimally adequate but could be more complete for a logs 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?

Schema description coverage is 0%, meaning the description should add meaning beyond the schema. However, it only repeats the parameter names and trivial descriptions (e.g., 'Web app name') without adding context like format, constraints, or examples. The baseline for 0% coverage is higher, but the description fails to compensate.

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 ('View') and the resource ('web app logs from Azure Monitor'). It is specific and distinguishes the tool from sibling tools like webapp_list and webapp_show, which have different purposes.

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 provides no guidance on when to use this tool vs. alternatives. It does not mention any prerequisites, limitations, or scenarios where other tools (e.g., get_activity_log, get_container_logs) might be more appropriate.

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