nexo_somatic_stats

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

No annotations exist. Description only states output, no mention of side effects, authentication, rate limits, or that it's a read-only operation. Minimal behavioral disclosure.

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?

Extremely concise at 5 words, covering two output components. Could include a verb for clarity, but overall efficient.

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?

No explanation of what 'somatic' refers to or what 'risk distribution' means. With no output schema, more context is needed. Lacks domain-specific interpretation.

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?

No parameters in schema, so description adds no param info. Since schema coverage is 100% and no parameters, baseline of 4 is appropriate; no need for compensation.

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 outputs 'Top 10 riskiest targets + risk distribution', which defines the tool's result. However, it lacks an active verb and does not explicitly say 'Get' or 'List', so it's slightly less direct but still clear.

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 versus siblings like nexo_somatic_check. No indication of prerequisites or context for use.

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