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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is covered. The description adds useful context by specifying the data fields returned (agent_type, versions, LLM config, counts) and the HTTP endpoint, going beyond the generic annotation hints. No contradiction with annotations.

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 sentence that front-loads the action and object, then compactly lists the key response contents and endpoint. There is no filler or redundancy; every word contributes meaning.

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?

This is a simple zero-parameter read tool with rich annotations and an output schema present. The description's enumeration of fetched fields and the endpoint, combined with the existing structured metadata, fully equips 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?

The tool has zero parameters and an empty schema, so schema coverage is trivially 100%. With no parameters to document, the description does not need to add parameter-level detail; the baseline of 4 for parameterless tools is appropriate.

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 uses the specific verb 'Fetch', identifies the resource as the 'selected bot record', and enumerates key contents (agent_type, versions, LLM config, related counts). It also includes the exact endpoint GET /v1/bot/get-data, making it clearly distinct from sibling list/update tools.

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 phrase 'selected bot' clearly indicates the tool operates on a currently selected bot, implying use after a selection step. However, it does not explicitly mention when not to use it or name alternatives such as get-bot-dashboard-stats or list-owned-bots, so it stops short of full guidance.

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