Get bot detail

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

The readOnlyHint annotation already signals a safe read operation, and the description adds meaningful behavioral context by listing the exact metadata fields returned. It also clarifies that transcript_id is the canonical source and that caption_file is provider-specific, which helps an agent interpret the result.

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 dense line with no wasted words. It front-loads the core purpose and then lists concrete return fields, with useful parenthetical clarifications for transcript_id and caption_file.

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?

For a simple single-parameter read-only tool, the description adequately explains what the agent will receive, including special cases like meeting_captions provider. It does not explain where bot_id comes from, but the low complexity and sibling tool context make this a minor 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 description coverage is 0%, and the description does not explain bot_id, its format, or how to obtain it. The single required parameter is easy to infer from the tool name, but the description adds no semantic value beyond the bare schema definition.

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 a specific verb-resource pair and immediately defines what the tool returns: full session metadata with enumerated fields such as platform, duration, timings, status timeline, transcript_id, caption_file, and original request payload. This clearly differentiates it from sibling tools like get_bot_status and get_bot_summary.

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 'Full session metadata' implies this is the tool to use when comprehensive session details are needed, but there is no explicit contrast with get_bot_status, get_bot_summary, or get_transcript. Usage is inferable rather than directly stated, and no when-not-to-use guidance is given.

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