AxonHub status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that this is a metrics retrieval operation, but it does not explain aggregation behavior, data freshness, pagination, or whether channel success rates depend on channelLimit. This is thin for a tool with no annotation safety profile.

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 with no wasted words. Every phrase adds information about what is retrieved, which is exactly the appropriate structure for a simple status tool.

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 metrics lookup with all optional parameters and reasonable schema descriptions, the description is minimally viable. However, with no output schema and no annotations, it leaves return format, sibling differentiation, and parameter interplay unexplained, which are clear gaps.

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 schema covers projectId and timeWindow descriptions but leaves channelLimit undocumented, and the description adds no parameter-level meaning. With 67% schema coverage, the description needed to compensate for the missing channelLimit semantics and clarify how timeWindow and channelLimit shape the returned metrics, but it does not.

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 specific verb and resource ('Get ... from the AxonHub dashboard') and lists the concrete metrics returned: request totals, latency, token totals, and channel success rates. However, it does not distinguish itself from the similar sibling axonhub_usage, so the differentiation criterion for a 5 is not fully met.

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 guidance on when to use this tool versus axonhub_usage or axonhub_list_requests. The description implies an overview/status use case but never states exclusions or alternative selection conditions, leaving the agent to infer the right context.

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