emoji_admin_list

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

No annotations are provided, so the description carries the full burden. It mentions 'undocumented session endpoint,' hinting at possible instability or session requirement, but does not disclose whether the operation is read-only, what side effects exist, or authentication needs.

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 (one sentence), but it is overly sparse, omitting critical details. Conciseness is positive, but not at the expense of necessary 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?

Given the tool has two optional parameters and an output schema, the description is severely incomplete. It does not explain pagination, the meaning of 'custom,' or how the response is structured. The output schema may help, but the description alone is lacking.

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 0%, so the description must explain the two parameters (page, count). However, it provides no information about their meaning, valid values, or behavior with defaults.

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?

Clearly states it lists custom emoji with metadata, which is a specific verb and resource. However, it does not differentiate from sibling tool 'emoji_list' which likely also lists emoji, but possibly not only custom ones.

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?

No guidance on when to use this tool versus alternatives like emoji_list. The description calls it an 'undocumented session endpoint,' implying it might be unstable or internal, but does not explicitly state when it should be chosen over other emoji listing tools.

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