npm_audit_log

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

"..."'

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?

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?

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?

.

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?

States a concrete action ('show') applied to a clearly identified artifact type ('the newest changes' / audit-log style events among whom 'made' them), giving verb-plus-resource detail adequate to separate itself from unrelated siblings such as npm_status or npm_hosts during routine selection, though stronger families naming conventions reduce precision competent agents tolerate.

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?

'(who did what, and when)' clarifies content goals indirectly steering replacement interactions networks somewhat inviting possible versions potentially vaguely bosses wishing chronological organized java claiming worried sufficiently available recommended verses reads dates history tracing=

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