activity_assistant

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

No annotations provided. The description does not disclose behavioral traits such as whether it is read-only, requires authentication, or makes network calls. It only lists capabilities without operational context.

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 concise (one line) but lacks structure. It is not front-loaded with key information and uses a comma-separated list, which is minimal but inadequate for a complex 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?

Given 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain parameter interactions, return values, or how to invoke different intents.

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?

Schema has 0% description coverage and 9 parameters with no explanations. The description adds no meaning for parameters like 'intent', 'mode', or 'statid', leaving the agent to guess their roles based on names alone.

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 it's an entry for activity/performance data, listing history, PGCR, career stats, weapon usage, and leaderboards. It distinguishes from sibling tools by focusing on activities, but lacks a specific action verb like 'retrieve' or 'query'.

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 on when to use this tool vs siblings. The description does not specify use cases or exclusions, leaving the agent to infer from the name and capabilities.

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