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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about input format, language assumptions, error behavior, or output. A single repeated word provides zero behavioral context.

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 short but not concise in any meaningful sense; it is a tautological repetition of the tool name with no front-loaded information, so its brevity reflects under-specification rather than efficiency.

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?

With no annotations, no output schema, and three overlapping ambiguous parameters (text/word/input all described as 'to process'), the description should explain what lemmatization returns and which parameter form is expected. It does none of this, leaving the agent to guess.

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%, so all three parameters (text, word, input) carry their own descriptions, establishing the baseline of 3 per the rubric. The description adds nothing beyond the schema, and notably fails to disambiguate the three near-synonymous parameters.

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 is the tautology 'Lemmatize: Lemmatize', which merely restates the tool name. While 'lemmatize' does denote a specific linguistic operation, the description adds no verb+resource framing, no scope, and no differentiation from the many sibling text tools (x402-stem, x402-stem-word).

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 when-to-use guidance, no distinction from alternatives such as x402-stem-word, x402-singularize, or x402-tokenize, and no conditions, inputs, or prerequisites mentioned.

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