Text-Toolkit

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

With no annotations provided, the description carries full burden but only states the basic transformation. It doesn't disclose behavioral traits like what 'Capital Case' means precisely, whether it handles special characters, what happens with empty input, error conditions, or performance characteristics. The description is minimal and lacks important operational 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 extremely concise at just 4 words. It's front-loaded with the core purpose and wastes no words. Every word earns its place by communicating the essential transformation.

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 4 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain the transformation details, parameter usage, return values, or edge cases. For a text transformation tool with multiple parameters, this minimal description leaves too much unspecified.

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 but fails to do so. It mentions no parameters at all, leaving all 4 parameters (text, delimiter, locale, mergeAmbiguousCharacters) completely undocumented. The description doesn't explain what these parameters do or how they affect the transformation.

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 verb 'Convert' and the resource 'text' with the specific transformation 'to Capital Case'. It distinguishes from some siblings like 'case_to_camel' by specifying the case type, but doesn't differentiate from all text transformation tools like 'string_replace' or 'regex_replace'.

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 provided on when to use this tool versus alternatives. The description doesn't mention when to choose this over other case conversion tools (like case_to_camel, case_to_snake) or general string manipulation tools. There's no context about typical use cases or limitations.

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