get_activity_log

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

No annotations are provided, so the description carries full burden. It mentions the tool is read-only (get) and describes filters, but lacks details on permissions, scoping (subscription-level?), pagination, or behavior when no logs are found. The description 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 concise with a one-line summary followed by parameter details. Every sentence adds value with no wasted words.

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 (likely detailing return format), the description doesn't need to explain return values. It covers the main purpose and filters, but could mention scope (e.g., subscription-level logs) or time range behavior. Overall adequate for a simple read 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%, but the description adds meaningful context: resource_group is optional, days has a range (1-7) and default of 1. This compensates for the schema's lack of descriptions, though it could clarify default behavior more.

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 gets the Azure activity log (audit log) and specifies optional filtering by resource group and days. It distinguishes itself from sibling tools like get_system_metrics or get_vm_status by focusing on audit logs.

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 for retrieving recent audit logs with optional filters but provides no explicit guidance on when to use this tool instead of alternatives. No exclusions or context is given.

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