get_user_sign_in_activity

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

The description mentions the required 'AuditLog.Read.All' permission, which is a key behavioral trait. However, it does not describe the nature of the response (e.g., single object with fields) or any side effects. With no annotations, the burden is higher, but the permission detail adds value.

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 a single, efficient sentence that conveys the core action and a critical requirement, with no unnecessary 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?

For a simple tool with one parameter and no output schema, the description covers the essence: what the tool does and the key permission needed. It could optionally hint at the return format, but it is largely 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?

The input schema already describes the 'identifier' parameter fully (UPN or object ID). The description adds no additional meaning beyond the schema, so with 100% schema coverage, baseline score of 3 is appropriate.

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 'Get last sign-in information for a user in Azure AD / Entra ID', providing a specific verb and resource that distinguishes it from sibling tools like get_user or get_device.

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 only mentions the required permission but does not provide explicit guidance on when to use this tool versus alternatives, nor does it exclude contexts where it would be inappropriate.

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