search_guild_messages

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

No annotations are provided, so the description must carry the burden. It only states 'native Discord search' which is vague. No mention of limitations, rate limits, authentication, or results format. Lacks behavioral detail.

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?

Description is very concise at one sentence, but it lacks structure like bullet points or emphasis on key aspects. It's efficient but could be better organized.

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 24 parameters, no output schema, and no annotations, the description is highly incomplete. It does not explain return values, pagination (offset/limit), or filtering options, leaving the agent with insufficient guidance.

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?

Description adds no meaning to the 24 parameters. Schema coverage is only 17%, so the description should compensate but does not. No parameter names or details mentioned.

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?

Description clearly states 'Search Discord guild messages' with a specific use case: 'Best for finding where a past discussion happened.' This is a specific verb and resource, and it distinguishes the tool's purpose from siblings like read_channel_messages or locate_message.

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?

Description gives a clear context for when to use: 'Best for finding where a past discussion happened.' However, it does not explicitly state when not to use or mention alternatives, but the sibling list provides some implicit differentiation.

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