get_guild

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond that—no mention of not-found behavior, permissions, rate limits, or return format. It is neutral and does not contradict the annotations.

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 short sentence that states the action and target without filler. It is well under any length concern and front-loads the most relevant information.

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 simple getter with two parameters, rich safety annotations, and no output schema, the description covers the core action and target. It does not specify behavior for missing guilds or timeout units, but these are secondary; the tool is adequately characterized for invocation.

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 schema_description_coverage at 0%, the schema offers no parameter descriptions. The description clarifies the purpose of guild_id through 'by ID,' but it does not address the optional timeout parameter, its unit, or its effect. This is insufficient compensation for the complete absence of schema-level parameter docs.

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 uses a specific verb ('Get'), a specific resource ('guild'), and scope qualifiers ('one', 'by ID'), which clearly distinguish it from the plural sibling get_guilds that presumably lists guilds. The singular target makes the tool's purpose unambiguous.

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 does not explicitly state when to use this tool versus alternatives like get_guilds. The 'by ID' phrasing implies the intended context (fetch a single guild when its ID is known), but it never names a sibling or exclusion condition, leaving the agent to infer the choice.

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