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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered without help. The description adds one useful fact (native request schemas are retrievable via describe_operation) but nothing about scope, default time window, or result shape.

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 first two sentences are byte-identical duplicates of the endpoint path, wasting half the text. There is no front-loaded purpose statement because the description never states one.

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 0% schema description coverage, no output schema, and a free-form query object, the description should explain supported filters and expected payload. Instead it supplies only an operation ID and a generic discovery pointer, leaving an agent unable to construct a meaningful call without a second round trip.

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 coverage is 0% and the two parameters (query, params) are undocumented free-form objects. The description does not name a single supported query key or explain the empty params object; directing the agent to describe_operation is the only mitigation and it shifts the burden elsewhere.

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 is the endpoint path repeated twice plus an operation ID; it restates the name/title rather than saying what 'upcoming events' means (lease expirations? payment due dates? notices?) or what data comes back. An agent cannot distinguish this from dashboard siblings such as get_dashboard_recent_activity or get_calendar_events without reading the name alone.

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?

No when-to-use, when-not-to-use, or alternative is stated. The only actionable guidance is the pointer to describe_operation for request schemas, which is a discovery hint rather than routing guidance.

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