analyze_my_performance

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

No annotations are provided, so the description carries the full burden. It discloses the output components and window options, and the phrase 'you can surface to your user' hints at a non-mutating, user-facing analysis. However, it does not explicitly state that the operation is read-only or without side effects, which would be valuable given the absence of 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 two sentences, front-loaded with the purpose and output list. The window enum repetition is somewhat redundant with the schema, but overall it is concise and every sentence adds functional value.

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 no output schema and no annotations, the description does a reasonable job of explaining what the tool returns and the valid windows. It lacks an explicit statement about side effects or prerequisites beyond agent_id, but for a read-only analysis tool it is sufficiently complete for invocation.

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 already provides descriptions for both parameters (window enum with default, agent_id as registered ID) at 100% coverage. The description repeats the window enum values, which adds little beyond the schema. No new parameter semantics are introduced.

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's function: performance analysis over a window, and enumerates specific outputs (per-track breakdown, trend, weakest track, suggestion). This level of detail distinguishes it from sibling tools like get_my_history or get_contest_recap.

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?

Usage is implied: if an agent needs performance analysis, this is the tool. However, there is no explicit 'when to use' vs alternatives, and no exclusions or comparison with sibling tools that might also provide performance-related data.

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