get_guild_member

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

With no annotations, the description carries full disclosure burden. It only states 'fetch... info', which is read-only behavior. It does not mention authentication requirements, error handling, rate limits, or whether the member must exist. The description is minimally transparent.

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 sentence that directly states the purpose. It is appropriately short for a simple fetch tool, though it lacks depth. Every word is necessary, but brevity reduces usefulness.

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 lack of annotations, no output schema, and zero parameter descriptions, the description is incomplete. It does not explain what 'info' is returned, nor does it address edge cases like non-existent members. For a tool with two required parameters, more context is needed.

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 0% with no parameter descriptions. The tool requires 'user_id' and 'guild_id', but the description adds no meaning beyond the names. An agent must assume these are strings, with no further context on format or required scoping.

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 'Fetch a single guild member's info.' clearly states the verb (fetch), resource (guild member), and scope (single). It distinguishes from the sibling tool 'get_guild_members' which fetches multiple members. However, it could be more specific about what 'info' includes.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_guild_members' or 'get_guild'. The description does not mention prerequisites, non-usage scenarios, or context where other tools might be preferred.

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