resource_impact_report

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

No annotations provided; description only says 'summarize', implying read-only but doesn't confirm side effects, permissions, or response format. Insufficient disclosure for a tool with no 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?

Single sentence is efficient but lacks structure. Could be improved with separate sections for parameters and behavior.

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 zero annotations, no output schema, and 2 undocumented params, description should provide more context on 'report partitions', 'top blockers', and 'impact metrics'. As is, incomplete for agent decision-making.

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 has 2 parameters with 0% description coverage; description does not explain min_age_minutes or limit, leaving their meaning entirely to the schema names.

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 'Summarize CPU/RSS impact, top blockers, and report partitions for related processes'. It specifies a verb and a distinct resource set but doesn't differentiate from siblings like process_scope_report or process_explain.

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 tool versus alternatives. Lacks context or conditions for invocation.

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