tokportal_get_analytics_dashboard

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds no behavioral information. It does not describe what data is returned, how filters interact, or any side effects. The description is entirely silent on behavior, which is a critical gap for a data-fetching tool.

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 extremely concise, consisting of a single sentence with no wasted words. However, it is so brief that it lacks substantive content, which is a trade-off. It is well-structured and front-loaded, but the brevity borders on under-specification.

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?

With no output schema, the description is the only source for understanding what the tool returns. It does not explain the dashboard's contents, the effect of filters, or any field details. Given six parameters and no behavioral guidance, this is severely incomplete for an effective tool description.

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 100% coverage, but the parameter descriptions are tautological ('query parameter to', 'query parameter from') and do not explain what the parameters mean. The description adds no additional interpretation. Given the low quality of schema descriptions, the tool description should compensate, but it does not, leaving the agent without meaningful parameter semantics.

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 'Get analytics dashboard' clearly indicates a verb+resource pair, but it lacks specificity about what the dashboard contains or how it differs from sibling tools like get_analytics_series, get_analytics_contract, or get_analytics_account. It is not a tautology, but it is too vague to distinguish from similar analytics tools.

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 alternatives. The description does not mention any context, prerequisites, or exclusions. It simply states the action without explaining the appropriate use case, leaving the agent to guess.

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