Analyze Text

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

No annotations are provided, putting the full burden on the description. The description does not disclose key behavioral traits such as whether the tool is read-only, requires authentication, has rate limits, or consumes credits beyond what is stated in parameter descriptions. It merely states the action without 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 a single sentence, which is concise but too brief given the lack of annotations. It is front-loaded but omits important details; the sentence is not wasted but could be expanded without losing conciseness.

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?

The description is incomplete for a tool with 3 parameters and no output schema or annotations. It does not explain the return value, how to retrieve results (especially given sibling zerotrue_get_result), or any behavioral requirements. The agent lacks sufficient context to invoke the tool correctly.

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%, so the schema already documents all parameters. The description adds minimal extra meaning beyond the schema, such as noting that isDeepScan and isPrivateScan 'can consume paid credits,' which is useful but not extensive. The text parameter is essentially repeated.

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 states the tool 'analyze[s] plain text for AI-generated content using ZeroTrue,' which clearly indicates the verb (analyze), resource (plain text), and purpose (detecting AI-generated content). It is specific enough to distinguish from sibling tools like zerotrue_analyze_file, but lacks explicit differentiation details.

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 provides no guidance on when to use this tool versus alternatives such as zerotrue_analyze_file or zerotrue_analyze_url. There are no prerequisites, exclusions, or context-specific recommendations, leaving the agent to infer usage from names alone.

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