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 conveys only purpose, not ordering details (e.g., newest-first), pagination behavior, or what the result objects contain, which matters for a list endpoint. For a zero-annotation tool, this is thin.

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?

Two front-loaded sentences with no filler. The purpose is stated first, followed by the use case.

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 a 2-param, no-annotation, no-output-schema list tool, the description covers the essential what and why. The missing pieces are ordering and distinguishing from the closely related sibling tools, which would materially help routing.

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 both limit and locale are fully documented in the schema, including the 1-25 bound and enum values. The description adds nothing beyond the schema, so the baseline 3 applies rather than a lower score.

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?

States a specific verb (get) and resource (most recently added Egyptian Arabic slang words) with a clear scope that distinguishes it from siblings like get_trending_words and get_word_of_day. An agent can immediately tell this is a recency-ordered list, not a search or 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?

The description says it is 'useful for seeing what new slang the community is documenting', which implies a discovery use case, but it never explicitly names when to use this versus get_trending_words or get_related_words. The sibling set is highly overlapping, so the absence of an explicit routing rule is a real gap.

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