technitium_stats

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

With no annotations provided, the description must carry the full behavioral burden. It implies a read-only retrieval of dashboard statistics but does not confirm read-only safety, mention permissions or rate limits, or describe any side effects. The behavioral profile is left largely to inference.

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 two short, front-loaded lines with no filler. The second line earns its place by enumerating period options, though the overall terseness leaves important usage context unaddressed.

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 one simple parameter and an existing output schema, the description covers the core return content and valid period values. However, without annotations, it should do more to state the read-only nature and when to prefer this tool over siblings; it is adequate but not complete.

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 description coverage is 0% and the sole 'period' parameter has no enum in the schema. The description compensates by listing the accepted values (LastHour, LastDay, LastWeek, LastMonth, LastYear), which is materially useful, though it omits the default value and any format details.

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 the resource ('dashboard numbers') and lists categories (queries, blocked, cached, top charts), but uses a noun phrase rather than a specific verb like 'retrieve' or 'get'. It does not explicitly differentiate from siblings such as technitium_blocking or technitium_resolve, leaving purpose inferable but not crisply stated.

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 given on when to use this tool versus alternatives like technitium_endpoints or technitium_call. The period value list is parameter detail, not usage context, so the agent receives no routing help.

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