discord_get_bot_identity

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

The 'Read-only' sentence merely restates readOnlyHint=true and earns no credit, but the description adds real behavioral context beyond annotations: it explains that identity splits into global scope vs. per-server scope, and that the per-server nickname/avatar is resolved 'in this guild' by guild_id. It omits permissions requirements and failure modes, which keeps it below a 5.

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 purpose is front-loaded and the four-facet breakdown is the substantive core. The intervening 'Read-only.' sentence duplicates the annotation and is the one line that does not earn its place.

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 one-parameter read tool with a full output schema and readOnly annotations, the description covers purpose, scope semantics, and pre-change usage. Nothing an agent needs to invoke it correctly is missing, though it could note that per-server fields are null outside a guild.

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?

With a single parameter at 100% schema description coverage ('Discord server (guild) ID (snowflake)'), the schema already carries the semantics. The description only implicitly hints that guild_id selects the per-server identity fields, adding marginal value over the schema baseline.

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 opens with a specific verb and resource: 'Report the bot's own identity.' It then decomposes that identity into four clearly named facets (global username/avatar, per-server nickname/avatar, application name/ID), which distinguishes it from siblings like discord_get_guild_info or discord_get_bot_permissions.

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?

'Use this before changing anything so you know which of the four you actually mean' gives a clear activation context tied to the identity-mutating siblings (discord_set_bot_nickname, discord_set_bot_avatar, discord_set_bot_username, discord_set_application_icon). It stops short of naming those alternatives or stating when not to call it.

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