email_logs_user

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

Since no annotations are provided, the description bears the full burden of behavioral disclosure, yet it only names the resource. It does not state that the operation is read-only, describe the log content or format, or mention pagination, filtering, session, or authorization requirements.

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 extremely short and front-loads the key scoping information with no filler. It is arguably under-specified for full understanding, but as a concise definition it uses every word effectively.

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 no-parameter, output-schema-backed read tool, the description is minimally viable: it identifies the resource and the scope. However, it leaves the meaning of 'impersonated' and the relationship to email_logs/email_logs_summary implicit, so an agent has only partial context for confident selection.

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 tool has zero parameters and schema coverage is vacuously 100%, so there is no parameter burden for the description to carry. The 'current/impersonated user' wording usefully clarifies the implicit scope that substitutes for parameters.

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 phrase identifies the resource (email logs) and a specific scope (current/impersonated user), which distinguishes it from sibling tools like email_logs and email_logs_summary. It lacks an explicit verb such as 'retrieve' or 'list', so it stops short of a fully explicit statement of action.

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 'current/impersonated user' implies this tool is for session-scoped email logs, but the description does not explicitly say when to prefer it over email_logs or email_logs_summary. It provides no exclusions, alternatives, or context about when this variant should be chosen.

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