core_stats

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

No annotations are provided, so the description carries the full burden. It states the tool returns a snapshot, implying a read-only operation, but does not explicitly confirm lack of side effects, permissions, or rate limits. With no annotations, a score of 3 is appropriate for 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?

The description is a single, well-structured sentence with a dash separating the title from the elaboration. It is front-loaded with 'Current stats snapshot' and contains no extraneous words.

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?

For a simple snapshot tool with optional parameters and no output schema, the description provides the core purpose and key return fields (bytes, speed, errors). It lacks details on the return structure or when specific parameters are useful, but it is largely sufficient for an agent to understand basic usage.

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 coverage is 100%, so the baseline is 3. The description adds no additional parameter details beyond the schema. While the schema describes each parameter, the description does not enhance understanding of their usage or impact on the snapshot.

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 clearly states the tool returns a 'Current stats snapshot' with specific statistics (bytes transferred, speed, error counts). The verb 'Returns' and resource 'stats snapshot' make the purpose explicit, and it distinguishes from sibling tools like core_stats_delete and core_stats_reset.

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 implies usage for obtaining current transfer statistics, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., core_transferred for specific transfer data). No exclusionary conditions or context provided.

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