tokportal_get_comment_pulse

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds no behavioral context beyond that, such as what 'pulse' means in terms of data aggregation, time windows, or rate limits. It does not contradict annotations but fails to improve transparency.

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 (4 words) but lacks structure and substance. While brevity is valued, here it sacrifices all meaningful information, making it more of a title than a useful description.

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 has 8 parameters, no output schema, and numerous sibling tools. The description provides no context about return values, parameter usage, or how this analytics tool differs from others. It is severely incomplete for an agent to use effectively.

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 8 parameters with descriptions that are trivial ('query parameter <name>'). The tool description does not explain any parameter semantics, such as the meaning of 'post', 'account', or the date range defined by 'to' and 'from'. It adds no value beyond the weak schema descriptions.

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 comment pulse analytics' is a minimal verb+noun phrase but does not define what 'comment pulse' is or how it differs from sibling analytics tools like tokportal_get_analytics_series. It lacks specificity and fails to distinguish the tool's unique purpose.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context that would help an agent decide between this and other analytics or comment-related tools.

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