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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only mentions 'offline', which indicates no network calls, but doesn't describe output format, error handling, or limitations. Minimal behavioral insight.

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 extremely brief, a single phrase. While front-loaded with the purpose, it omits critical details about the parameter and usage, making it under-specified rather than appropriately concise.

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 tool with one parameter and an output schema, the description fails to explain the parameter or provide usage examples. It is incomplete for an agent to correctly invoke the tool without guessing what 'q' should be.

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 sole parameter 'q' is undocumented in the schema (0% coverage) and the description doesn't mention it. It's unclear whether 'q' should be an emoji, a unicode name, or a codepoint. No input format guidance is given.

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 it's an emoji lookup tool that maps between emoji and Unicode name/codepoint, with 'offline' indicating local operation. It is specific and not a tautology, though it doesn't explicitly differentiate from the similar sibling 'unicode_lookup'.

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 is given on when to use this tool versus alternatives like 'unicode_lookup' or other lookup tools. There is no mention of scenarios that would select this tool over others.

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