app_emojis_get

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds the return shape and a 'verify exists' use case, but no additional behavioral context like error handling or permissions. No contradictions with 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 very concise, front-loaded with the purpose, and well-structured with clear sections for purpose, when to use, and returns. Every sentence serves a functional role with no redundancy.

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 fetch operation with complete schema, rich annotations, and an output schema, the description provides adequate context including purpose and practical use cases. It is fully complete for an agent to select and invoke the tool correctly.

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 covers both parameters (application_id and emoji_id) with descriptions, providing 100% coverage. The description does not add any extra meaning beyond what the schema already includes.

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 explicitly states 'Fetch a single application emoji' with a clear verb and resource. It distinguishes itself from sibling tools like app_emojis_list by focusing on a single item and from guild emoji tools by specifying 'application' scope.

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 'When to use' section provides clear scenarios (verify existence, inspect name/animated flag). However, it does not explicitly mention alternatives or when not to use it, such as when to prefer emojis_get or app_emojis_list.

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