discord_emoji

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention the body.image data URI for create, but it fails to disclose that dryRun defaults to true, that confirm may be required for destructive actions, or any permission requirements or side effects.

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 a single, front-loaded sentence with no wasted words. It is concise and immediately communicates the CRUD scope, though it could benefit from additional sentences to clarify key parameters and safety behavior.

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?

The tool performs four distinct actions, has 7 parameters including a nested body object, and has no output schema. The description only scratches the surface, omitting how list results are returned, the meaning of dryRun and confirm, and how modify/delete identify their targets. This is substantially incomplete for a tool of this complexity.

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 compensate for all 7 parameters. It only adds meaning for body.image in the create action. The roles of guildId, action, dryRun, confirm, emojiId, reason, and the body object are left to the schema, with no additional explanation.

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 clearly states the tool's function with specific verbs ('List, create, modify, or delete') and a specific resource ('guild emojis'). This distinguishes it from sibling tools that target channels, roles, messages, or guild settings.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, and no exclusions. The description only lists what operations are possible without explaining under what circumstances each should be chosen.

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