get_system_stats

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

No annotations are present, so the description alone must convey behavior. It discloses that the tool returns three types of information, indicating a safe read operation. Nonetheless, it lacks details on data freshness, caching, or potential errors, which would aid agent decision-making.

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, front-loaded sentence that immediately states the tool's purpose. Every word contributes value, with no superfluous content.

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 tool is simple with no output schema. The description lists three returned fields with 'including', implying incompleteness. For full completeness, it should explicitly state all return values or confirm the list is exhaustive.

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 input schema has zero parameters, so the description's role is to clarify what the tool returns. It adds meaning by enumerating the returned statistics beyond the empty schema, which is perfectly appropriate for a parameterless tool.

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 uses the specific verb 'Get' and identifies the resource as 'overall statistics of the HimiTrace system'. It explicitly lists included data points (total registered products, wallet balance, contract info), which clearly distinguishes it from sibling tools that focus on specific items like products or certificates.

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 system-level overviews by listing global statistics, contrasting with siblings that target specific entities. However, no explicit guidance on when to use this tool versus alternatives or when not to use it is provided.

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