get_guild

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

With no annotations, the description carries the burden of behavioral disclosure. It correctly implies a read-only detail fetch and lists what kinds of data are included, but it does not mention errors for invalid IDs, permissions requirements, rate limits, or how with_counts changes the response. It provides some behavioral context but leaves notable gaps.

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 well-structured sentence with no filler. It front-loads the primary action and resource, then gives concrete examples of what the details include. Every phrase adds value.

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 relatively simple getter with fully documented parameters, the description provides enough to understand the tool's role and expected output shape. Since there is no output schema, the enumerated response contents (roles, emojis, member count) help compensate for that absence, though error and edge-case behavior is not addressed.

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 100%, so both parameters are already documented. The description reinforces that guild_id identifies the target server but adds no new meaning for with_counts. Baseline 3 is appropriate because the schema already does the work.

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 names a specific verb ('gets'), a specific resource ('details of a specific Discord guild/server by its ID'), and concrete detail categories (roles, emojis, member count). This clearly distinguishes it from list_guilds, which would be about multiple guilds rather than one targeted by ID.

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 establishes clear context: use this when you have a specific guild ID and need its details, rather than listing guilds. It does not explicitly name the sibling list_guilds as the alternative or state when not to use it, but the 'by its ID' phrasing makes the intended scope obvious.

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