check_ethics

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

The description provides no behavioral traits such as whether it reads or modifies state, what it returns, or side effects. With no annotations to rely on, the description carries full burden and fails entirely.

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 extremely short but under-specified. It does not earn its place as it provides no useful information beyond the name.

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, no annotations, and a single vague word, the description is completely inadequate for an agent to understand its purpose or behavior. It leaves all questions unanswered.

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 tool has zero parameters and schema coverage is trivially 100%. No parameter information is needed, but the description adds no context about what the tool checks without inputs. Baseline score applies due to zero-parameter nature.

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 'IRB Neural Welfare Check' is a vague noun phrase without a verb. It fails to specify what action the tool performs (e.g., check, verify, report) or what resource it acts on. Among many sibling tools with similarly cryptic names, this does not distinguish itself.

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 alternatives like get_metrics, get_system_status, or tcai_emotion_appraise. There is no mention of prerequisites or context.

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