ywm_add_original_text

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

No annotations are provided and the description gives no behavioral details. For a mutation tool ('add'), there is no mention of side effects, authorization needs, or idempotency, leaving the agent blind to important traits.

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 very concise (3 words), but it lacks informative content. While brevity is generally positive, the extreme shortness here results in under-specification. Every word should earn its place, but here the sentence is too terse to be useful.

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 moderate complexity (2 params, 1 required, no output schema, no annotations), the description is incomplete. It does not explain the purpose of 'original text', the response format, or how this tool fits into the broader workflow.

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% with clear parameter descriptions for 'content' and 'host_id'. The tool description does not add any meaning beyond what the schema already provides, so the baseline score of 3 applies.

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?

Description states verb+resource ('Add original text'), but 'original text' is undefined and does not distinguish from sibling tools like 'ywm_get_original_texts' or 'ywm_delete_original_text'. The purpose is clear in a narrow sense but lacks semantic specificity.

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 on when to use this tool vs. alternatives, prerequisites (e.g., host_id requirement), or context. The description provides no usage direction.

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