debug_manifest

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Raw manifest breakdown' does not reveal whether the tool is read-only, what 'raw' entails, whether it returns large or sensitive data, or any side effects. This is a serious transparency gap, as the agent receives no safety or behavior cues.

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 extremely short, but this is under-specification rather than effective conciseness. It consists of five words and lacks a complete sentence, omitting critical details. While concise in length, it fails to earn its place by providing meaningful guidance.

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 no output schema and no annotations, the description must explain the tool's behavior, return value, and use context. It does not do so. The schema covers parameters well, but the overall tool remains opaque. The description is inadequate for an agent to understand what to expect or when to invoke this tool.

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 parameter schema fully documents both parameters, including defaults and token format, achieving 100% coverage. The description itself adds no parameter semantics, but the baseline of 3 applies because the schema effectively explains the parameters. The description does not need to repeat what the schema already 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?

The description 'Dev visibility: raw manifest breakdown' is a fragment lacking an explicit verb or action. It vaguely suggests the tool provides a raw manifest breakdown for developers, but does not clearly state what the tool does (e.g., retrieves, displays, lists). It also fails to distinguish itself from sibling tools like list_manifest or verify_manifest.

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?

There is no guidance about when to use this tool versus alternatives. The description provides no context for appropriate use cases, prerequisites, or exclusions. It is a bare phrase with no directional information for an agent selecting among similar tools.

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