Get platform activity logs

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. However, the description adds no additional behavioral context, such as what the logs contain, how they are structured, or any rate limits or pagination behavior. It contributes no value beyond the annotations.

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 with no wasted words, but this is under-specification rather than effective conciseness. It is appropriately front-loaded but lacks substance, making it minimally acceptable.

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 one free-form query parameter and no output schema, requiring the description to clarify usage and return behavior. The description is only a bare restatement of the tool's purpose, leaving agents unable to construct a meaningful request or interpret a response. This is a significant completeness gap.

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 includes a single 'query' parameter that is an open-object with arbitrary key-value pairs, yet the description provides zero explanation of how to use it. With schema description coverage at 0%, the description completely fails to compensate, leaving the agent without any insight into valid query fields or expected format.

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 clearly states the tool retrieves platform activity logs, using a specific verb ('Get') and resource ('platform activity logs'). It is sufficiently distinct from the sibling tools at a basic level, though it does not explicitly differentiate itself from other log-related tools like cymulate_platform_trace_log.

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 the many sibling tools, nor any context about the intended use case. There are no exclusions, prerequisites, or examples of appropriate usage scenarios.

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