ai_moderate

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

With no annotations, the description bears full transparency burden. It discloses that the tool is free and requires a service key, which are useful behavioral traits. However, it omits details like side effects (none expected), rate limits, or the nature of the 'flagged status' output.

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?

Two concise sentences that front-load the purpose and result. No superfluous words; every clause adds value.

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 no output schema, the description briefly mentions the return types (flagged status and category scores), which covers the essential output. It could be improved by specifying the data structure or providing an example, but the description is adequate for basic understanding.

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?

Input schema has 100% description coverage for both parameters. The tool description adds no extra parameter-specific meaning beyond the schema; it only restates the text parameter implicitly. Baseline of 3 is appropriate.

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 clearly states it runs content moderation on text, returning flagged status and category scores. It uniquely identifies the resource (text) and action (moderate), distinguishing it from sibling tools like 'ai_translate' or 'generate_image'.

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?

Provides auth requirement (service key) and cost (free for all projects), which offers basic context. However, it does not specify when to use this tool versus alternatives, nor does it mention any constraints or when not to use it.

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