extract_perfetto

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

Annotations are all false, providing no clear safety profile, so the description carries the burden of behavioral disclosure. It mentions running queries through a local processor, which suggests a read-style operation, but does not disclose side effects, permissions, data volume, or output behavior. No direct contradiction with annotations, but little added 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?

The description is a single, concise sentence with no redundant wording. It is appropriately front-loaded with the main action, though it sacrifices informative detail for brevity.

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 underdocumented parameters, a large sibling toolset, and minimal annotations, the one-line description is insufficient. The output schema exists, so return values do not need elaboration, but parameter semantics, usage context, and behavioral details are missing, making reliable invocation difficult.

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 description coverage is 0%, and the description provides no meaning for the two parameters 'run_id' and 'artifact_id'. The phrase 'versioned curated queries' vaguely implies query selection but does not map to either parameter, leaving the agent without sufficient semantic grounding.

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 action ('Run') and resource ('versioned curated queries through a configured local Trace Processor'), with the tool name 'extract_perfetto' providing domain context. However, 'versioned curated queries' is vague and does not specify what data is produced or how this differs from sibling extraction tools.

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 other extract_* tools, nor are alternatives mentioned. The phrase 'configured local Trace Processor' hints at prerequisites but gives no exclusions or decision criteria.

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