pm_troubleshoot_quick_scan

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

No annotations provided, so description must carry full burden. Only lists components without explaining behavior like side effects, aggregation of results, or potential performance implications. Lacks critical transparency for a composite action.

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?

Very concise single sentence, but under-specified for a composite tool. Should expand to include parameter info, usage context, and behavioral notes.

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?

Although output schema exists, the description omits crucial context like what 'composite' means, the order of operations, or any caveats. Incomplete for a multi-step tool with no annotations.

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%, yet the description provides no explanation for any parameter. file_path and compute_hash are left completely undocumented, forcing the agent to infer meaning.

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?

Description clearly states it is a composite triage combining file info, expert, top conversations, TCP anomalies, and protocol hierarchy. This distinguishes it from individual sibling tools, but lacks an explicit action verb like 'run' or 'perform'.

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 composite tool versus its siblings, especially pm_troubleshoot_flow which may have similar purpose. No context for ideal use cases.

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