api_get_v2_email_activity

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no behavioral context beyond repeating the HTTP method (GET), which is already implied by the annotations and tool name. It does not mention return format, authentication needs, rate limits, or any operational nuances, providing zero additional 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 extremely short, but this is under-specification rather than effective conciseness. A single phrase that restates the endpoint adds little value and fails to inform the agent about the tool's purpose, usage, or behavior.

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 no output schema and minimal description, the tool lacks essential context about what data is returned, what 'email activity' encompasses, and how to interact with it. Given the large set of sibling tools, this sparse description is insufficient for an agent to select and invoke the tool correctly.

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 100% with both parameters (email, dry_run) having descriptions. The tool description itself adds nothing about parameters, but the schema already documents them adequately, meeting the baseline for high schema coverage.

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 'GET /api/v2/email/activity — Активность' essentially restates the tool name and endpoint without explaining what the tool does. It does not specify what 'activity' means, what data is returned, or how it differs from siblings. This is a tautological description that fails to add clarity beyond the name.

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?

There is no guidance on when to use this tool versus alternatives like get_delivery_status, get_issue_stat, or other activity-related tools. The description gives no context about typical use cases, prerequisites, or exclusions, leaving the agent without direction.

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