process_text_api_v1_retrieval_process_text_post

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

The description lacks any disclosure of behavioral traits such as side effects (e.g., does it mutate data?), authentication requirements, rate limits, or idempotency. With no annotations, the description carries the full burden, but it provides zero useful information beyond the tool name.

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?

While the description is extremely brief (two words), it is under-specified rather than concise. It omits critical information that could be conveyed efficiently, so it does not earn its place as a useful description.

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 complexity of the tool (3 parameters, retrieval context, no output schema, and numerous sibling tools), the description is entirely inadequate. It provides no context about return values, processing behavior, or how to use the parameters effectively.

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 has 3 parameters with 0% description coverage, and the description does not explain what 'collection_name', 'content', or 'name' represent or how they affect processing. The description fails to compensate for the lack of schema documentation.

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 'Process Text' is a tautology that merely restates the tool's name and title without specifying what type of processing (e.g., indexing, analyzing, transforming) is performed or on what kind of text. It fails to differentiate from sibling tools like process_file, process_web, or query_collection.

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 alternative process or query tools. There is no indication of prerequisites, context, or exclusions, leaving the agent to guess the appropriate use case.

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