discord_get_bot_profile_limits

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

readOnlyHint=true and openWorldHint=false already declare the safety profile, so 'Read-only' is restated rather than added. What the description does contribute is the source of truth ('from the live client state') and the semantic framing that the result is a documented limitation rather than an absence of tooling. Return shape is covered by the output schema, so no gap there.

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?

Two sentences, both front-loaded with the operative information (what it explains, then when to reach for it). The closing 'documented limitation, not a missing tool' clause is behavioral guidance an agent needs, not filler.

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 no-arg, read-only introspection tool with an output schema and annotations already covering safety, this is complete: purpose, trigger, data source, and interpretation of the result are all present.

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?

Zero-parameter tool, so no parameter meaning is required; baseline 4 applies. The description correctly implies the only input is the ambient server/bot context, with no argument needed.

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 and resource: explains, from live client state, which profile parts this server can/cannot change and why. This clearly separates it from the setter siblings (discord_set_bot_avatar, discord_set_bot_username, discord_set_bot_guild_avatar) and from discord_get_bot_identity, which reports identity rather than limits.

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?

Gives an explicit trigger ('when asked to change the bot's banner, its "about me", or anything else Discord does not expose to bot accounts') and states the expected outcome so the agent does not fall through to a nonexistent setter. Explicit when-to-use plus an alternative interpretation of the failure case.

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