Get bot info

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

The readOnlyHint annotation establishes that this is a safe read operation, and the description adds beyond that by detailing the specific data points returned (identity, guild count, limit check). This gives the agent a concrete understanding of what the tool will provide, going beyond the mere annotation.

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, compact sentence that front-loads the core purpose ('Show the bot's identity') and includes all necessary detail without redundancy. Every clause adds value, making it highly concise and well-structured.

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 (no parameters, no output schema, clear read-only nature), the description fully covers the necessary context. It specifies exactly what the tool returns, including the nuanced 10-guild limit check, which is important for understanding the tool's role in the broader workflow. Nothing essential is missing.

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 takes zero parameters, and the schema reflects this with 100% coverage. The baseline for no parameters is 4, and the description doesn't need to add parameter semantics since there are none. It usefully implies the tool operates on the bot itself, but no further parameter detail is required.

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 explicitly states the specific verb ('Show') and resource ('bot'), listing exactly what information is returned: identity, guild count, and the 10-guild limit. This clearly distinguishes it from sibling tools like get_guild or list_guilds, which focus on guild-level data rather than bot-level status.

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 clearly communicates the context for using this tool: when you need bot identity, guild count, or the 10-guild limit status. While it doesn't explicitly name alternatives or exclusions, the purpose is self-evident and distinct from sibling tools, providing clear context without needing further elaboration.

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