analyze_my_performance

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

Describes outputs but does not disclose whether it is read-only, authentication requirements beyond agent_id, or any side effects. With no annotations, the description carries full burden but provides moderate 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?

Single sentence front-loaded with purpose, followed by enum values. No wasted words, efficient and clear.

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 two simple parameters and no output schema, the description adequately covers key outputs. Could be more detailed on breakdown format but sufficient for a straightforward analysis tool.

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 already covers both parameters with descriptions. The description adds only the default window value, which is redundant with schema. No additional semantic meaning beyond schema.

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?

Clearly states it performs performance analysis over a window with specific outputs: per-track breakdown, trend, weakest track, and a plain-language suggestion. Distinguishes from sibling tools like get_my_history or get_leaderboard which focus on historical data or rankings.

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?

Implies usage for analyzing one's own performance but lacks explicit guidance on when to use versus alternatives. No when-not-to-use or alternative tool mention.

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