find_long_words

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

The only behavioral disclosure is the cost of $0.001 USDC via x402, which is useful but insufficient. With no annotations and no description of input/output, side effects, or limits, the description fails to disclose essential behavioral traits for a tool that presumably processes text.

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 brief and free of verbose filler, but it is under-specified. The phrase 'Other Utilities tool' adds no real value, and the description lacks structure or detail that would make the brevity effective.

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 lack of annotations, an output schema, and meaningful parameter definitions, the description is severely incomplete. An agent would not know what input to provide or what to expect in return, making the tool effectively unusable based on this description alone.

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 input schema only contains a generic 'params' object with a placeholder description. The tool description adds no information about actual parameters, such as how to specify the text or define 'long'. The description does not compensate for the schema's lack of concrete parameter detail.

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 'find long words' simply restates the tool name without explaining what constitutes a long word, what input is expected, or what output is produced. It does not meaningfully distinguish itself from the sibling 'find_short_words' beyond the obvious opposite wording.

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. The description only mentions cost and the generic 'Other Utilities' category, which provides no contextual or selection criteria.

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