novai_transparency

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

No annotations are provided, so the description carries the full behavioral burden. It lists content categories but does not disclose whether the operation is read-only, whether the metrics are static or current, whether authentication is required, or what the response looks like.

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 short sentence fragment with no wasted prose, but it is under-specified rather than effectively concise. It front-loads the topic area but not an actionable verb or scope.

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 zero-parameter tool, the description gives a minimal indication of the metric areas covered. However, with no annotations and no output schema, it should more clearly state what is returned and whether the values reflect current platform policy.

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 full schema coverage, so there are no parameter semantics for the description to clarify. The baseline for a parameterless tool applies.

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 names a resource area, 'Platform hard metrics,' and lists topics such as fee, multiplier, refunds, and limits, but never states the operative verb (retrieve, return, display) or clarifies what 'hard metrics' means. It also does not distinguish this tool from siblings like novai_pricing_feed, leaving the exact purpose only partially inferable.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The agent must infer usage from the name and the terse metric list.

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