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

Annotations already establish a read-only, non-destructive, open-world profile, and the description adds meaningful context: the auth requirement (Cotlet API key with access to this app) and the specific figures returned, which matters since there is no output schema. It doesn't discuss rate limits or pagination, but this is a solid additive layer.

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 metric list is enumerated twice in consecutive sentences, which is pure redundancy and inflates the description. The period/auth guidance is front-loaded well enough, but the repeated enumeration costs it.

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, describing the returned figures is genuinely valuable, and the auth requirement plus period semantics round out what an agent needs to call it correctly. Only the absence of any output shape (e.g., array vs object of leads-by-source) is a residual gap.

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 100%, so period/from/to semantics are already documented, and the description largely repeats that ('default is last week; use custom with from and to'). It adds the default value context but nothing about format constraints beyond the schema.

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?

States a specific verb and resource (returns the Data Dashboard figures) and enumerates the actual metrics returned, so an agent can tell it apart from rently_list_leads, rently_get_lead, and rently_export_report. The opening line largely restates the title, which weakens the differentiation slightly.

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?

Explains the default period (last_week) and that custom requires from/to, which is useful selection guidance. However, it never contrasts this tool with sibling reporting tools like export_report or get_property_activity, so the agent must infer when this dashboard is the right choice.

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