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

Annotations already disclose readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the endpoint (POST /v1/bot-dashboard-stats) and optional date parameters, but no further behavioral context like authentication or response formatting. With annotations handling the key behavioral traits, this is adequate but not particularly rich.

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, efficient sentence that conveys the action, endpoint, and optional parameters. No filler or redundant content, and it is front-loaded with the core purpose ('Fetch bot analytics').

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?

Given the tool's simplicity (2 optional params, no required fields), the presence of an output schema, and annotations that cover read-only behavior, the description is complete enough for an agent to select and invoke the tool appropriately. It does not need to explain return values since an output schema exists.

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%, and both parameters already have clear descriptions ('Range start date in YYYY-MM-DD format' and 'Range end date...'). The description merely says 'optional date_from and date_to' without adding any additional semantic value beyond what the schema provides. Baseline 3 applies.

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 the tool's purpose: 'Fetch bot analytics' via a specific endpoint, with the scope (analytics/dashboard stats) distinguishing it from sibling tools like get-bot-details or list-owned-bots. It uses a specific verb and resource, leaving no ambiguity about what it does.

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 description implies usage context ('fetch bot analytics') and mentions the optional date range, but does not explicitly state when to use this over sibling tools or provide exclusions. It gives clear context without alternative guidance, which fits a 'clear context, no exclusions' scenario.

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