timps_api_perf_profiler

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description lists analysis outputs but does not disclose side effects (e.g., whether it only reads logs or mutates anything), required permissions, performance impact of running the profiler, or limitations (e.g., truncation, sampling). As a profiling tool, it likely performs read-only analysis, but nothing confirms this, leaving a substantial gap.

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, concise sentence front-loading the core action ('Profile an API') and then listing expected outputs. It is efficient and avoids fluff, but could be slightly better structured by separating the core purpose from the output list for greater readability.

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 moderate complexity (2 simple parameters, no output schema, no annotations). The description covers the main purpose but lacks details on return format, data sources specifics, or how to phrase requests. Given the schema is simple and no output schema exists, the description is minimally adequate but misses guidance on what 'access logs / traces' means or what 'concrete optimisations' entails.

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 coverage is 100%, with two simple parameters: 'request' (plain-language task) and 'language' (primary programming language, default python). The description adds context on the overall task (profiling) but does not detail how 'request' should be phrased or how 'language' affects profiling (e.g., impacts parsing of logs). With full schema coverage, baseline is 3; description does not add meaning beyond the schema, so 3 is appropriate.

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 states a specific action ('Profile an API') with a clear resource ('access logs / traces') and enumerates expected outputs (p50/p95/p99 by endpoint, slow query, N+1 detection, optimisations). This is specific and distinct from siblings like timps_sql_optimizer or timps_tech_debt_quantifier, which target different concerns.

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 implies usage for performance profiling of APIs using logs or traces, which suggests a suitable context. However, it does not explicitly state when to use this tool versus alternatives like timps_sql_optimizer or timps_log_interpreter, nor does it give exclusions or prerequisites (e.g., need for access logs). The implied usage is clear enough for a basic scenario, but lacks explicit guidance.

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