app_emojis_get

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

Annotations already declare this read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: it shows the return shape `{id, name, animated}` and explains that omitting application_id targets the authenticated bot's application. No contradiction with annotations exists.

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 compact, well-sectioned, and front-loaded with purpose. Every sentence earns its place: use cases, optional parameter behavior, and return shape. There is no filler or 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 read-only fetch tool, this is complete. An agent knows exactly what it does, when to use it, what the optional parameter means, and what it will get back. The existing output schema and annotations cover the remaining details.

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 description coverage is 100%, with both emoji_id and application_id already documented. The description's note about omitting application_id essentially restates the schema description and adds no new parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb and resource: 'Fetch a single application emoji.' It further clarifies the use case by saying it verifies existence and inspects the name/animated flag, which distinguishes it from list/create/modify/delete app emoji tools and from guild emoji tools.

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?

A dedicated 'When to use' section provides explicit conditions: verify an app emoji exists or inspect its name/animated flag. It also explains the important optional application_id behavior. It does not explicitly name sibling alternatives or exclusion cases, so it stops short of a full 5.

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