inspiration_emoji_gg_search

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint:false), the description adds substantial behavioral disclosure: it makes an external request only when invoked, sends no Discord token or query to Emoji.gg, matches queries locally, and warns about third-party metadata and license review. This goes well beyond what annotations already provide.

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 well-organized into five labeled sections (Purpose, External request, Safety, Search quality, Returns) and every sentence delivers relevant information without redundancy. It is appropriately sized for the tool's complexity and front-loads the core purpose.

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 search tool with external integration, the description is remarkably complete: it covers purpose, external behavior, privacy, safety/licensing, search limitations, and return structure. The output schema existence is supplemented by the explicit return format, making it highly self-sufficient.

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?

The schema already covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds valuable semantics by explaining that multi-word natural-language queries are matched locally against names/slugs and that user-submitted descriptions are not used for relevance, enhancing understanding of the query parameter beyond the schema.

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 opens with a clear, specific purpose: 'Search Emoji.gg for custom-emoji inspiration without changing Discord.' It names the external resource (Emoji.gg), the action (search), and the intended use case, which distinguishes it from Discord-native emoji tools like emojis_get or emojis_list_guild.

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 provides clear context for when to use it: 'before downloading or using `emojis_create`', and explicitly states what it does not do ('never downloads, uploads, or imports an emoji'). However, it does not name alternative tools or offer explicit when-not-to-use guidance, so it stops short of a 5.

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