trimend

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

With no annotations, the description carries full behavioral burden. It discloses the default behavior (whitespace by default) but misleadingly mentions 'specified characters' while the input schema has zero parameters. It does not address side effects, return values, or edge cases, leaving the behavior partially unspecified.

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 a single, focused sentence that conveys the core functionality with no wasted words. It is appropriately sized for a simple string operation.

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?

Despite being a simple tool, the description is incomplete because it implies a character-specification feature that the schema does not support. With no output schema and no annotations, the description should clarify the exact behavior and any limitations, but it does not, creating a gap between expectation and reality.

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 schema has zero parameters, so the baseline is 4, but the description introduces a nonexistent parameter by saying 'or specified characters,' which contradicts the schema. This actively confuses an agent expecting a parameter to control characters, so the description adds negative value.

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 that the tool trims from the end of a string, using the specific verb 'trim' with the resource 'end of a string.' This distinguishes it from siblings like 'trim' (both ends) and 'trimstart' (start), though it doesn't name them.

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 implies when to use this tool (when you need to trim from the end), but provides no explicit alternatives or exclusions. There is no mention of using 'trimstart' or 'trim' for other trim operations, so the guidance is only implicit.

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