nexus_audit_manifest

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows this is a safe, non-mutating operation. The description adds behavioral context by enumerating the specific risk heuristics (typosquatting, unpinned versions, abandoned packages), which clarifies the tool's analytical scope beyond a simple dependency listing.

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, compact sentence that is front-loaded with the core purpose and immediately enumerates the heuristics, providing maximum information per word.

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?

For a read-only, zero-parameter tool with annotations covering safety, the description covers the essential purpose and risk categories. It lacks an explicit output format, but no output schema exists, and the description is sufficient for an AI to understand when to invoke it.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly does not attempt to document parameter details. Schema coverage is trivially 100%, and no parameter semantics are needed.

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 identifies the tool as a dependency inventory with risk heuristics, distinguishing it from the sibling nexus_dependency_graph by focusing on typosquatting, unpinned versions, and abandoned packages. While it lacks an explicit verb, the intent is unambiguous.

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 use cases (auditing dependencies for supply-chain risks) but does not explicitly state when to choose this over alternatives like nexus_dependency_graph or nexus_impact_analysis. No exclusions or alternative tool guidance is provided.

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