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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful context by enumerating exactly what data is returned (profile, config, instructions, channels, integrations). No error or auth behavior disclosed, but the field-level return context is valuable.

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?

One sentence, front-loaded with the core action and resource, followed by a clean colon-separated enumeration. Every element earns its place by reducing the gap left by the absent output schema.

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?

Read-only getter with a single optional parameter fully documented, rich annotations, and no output schema. The description compensates by enumerating returned fields, making it complete enough for correct invocation. Minor gaps: no not-found/error behavior mentioned.

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% with one optional parameter (chatbotId) fully documented including pattern and session-default behavior. The description adds no parameter-level meaning beyond the schema. 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?

States a specific verb ('Get') and resource ('one chatbot's profile and configuration'), then enumerates the exact fields returned. Clear enough to distinguish from list_chatbots by the singular 'one', but doesn't explicitly name alternative siblings.

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?

Usage is implied: use this to inspect a single chatbot's full config. No explicit when-to-use vs alternatives, no prerequisites, no exclusions. The schema hints at the 'omit ID uses session context' behavior, but that's schema-level guidance, not description-level.

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