list_my_auth_activity

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

Annotations already declare readOnlyHint=true, so the description adds scoping context ('current user') but does not describe pagination, sorting, or the nature of returned activity. This is consistent with the annotations, providing minimal additional behavioral transparency.

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, clear sentence with no extraneous wording, front-loaded with the main action and 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?

With an output schema present, the return shape is covered. However, the description lacks guidance on pagination parameters (all four are undocumented in both schema and description), and does not clarify what 'authentication activity' includes. It is minimally sufficient for a simple list tool but has clear gaps.

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% for the four pagination parameters (page, size, sort, unpaged). The description does not mention or explain any of these parameters, leaving the agent without any added semantics beyond the parameter names.

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 'List authentication activity for the current user', which is a specific verb+resource scope. It distinguishes itself from the sibling tool 'list_auth_activity' by explicitly scoping to the current user.

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 scope 'for the current user' implies it should be used over the sibling 'list_auth_activity' when the agent needs the caller's own activity, rather than an admin view of all activity. However, this is only implied, not explicitly stated.

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