analytics_get_current_user_data

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Get' implies read-only, but the description does not explain what data is retrieved, whether authentication or specific permissions are required, or how 'real-time' behavior might affect results. The behavioral context is minimal.

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 very brief but under-specified. It reads more like a label than an explanatory description. The single sentence does not provide enough useful information to earn a higher score for structure.

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?

Despite having an output schema, the description fails to clarify what 'real-time agent data' actually includes. The ambiguous resource combined with zero parameter explanation makes the tool 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 description provides no explanation of the parameters (instance_id and queue_ids). With schema description coverage at 0%, the description must compensate but does not—it never mentions what these parameters control or how they affect the returned data.

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 uses a specific verb 'Get' and identifies the resource as 'real-time agent data,' but the resource is vague—'agent data' could mean metrics, status, or profile information. It does not clearly distinguish from sibling analytics tools like analytics_get_metric_data or get_current_metrics.

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 provided on when to use this tool versus alternatives. The 'real-time' qualifier hints at a use case, but there are no explicit when-to-use or when-not-to-use instructions, nor any mention of sibling tools or conditions that would make this the preferred choice.

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