collect_diagnostic_snapshot

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

The description notes that sections are independent so one unavailable data source does not lose the rest. With no annotations, this adds some behavioral insight, but it does not disclose read-only nature or potential side effects.

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 concise with four sentences: purpose, list of contents, behavioral trait, and follow-up guidance. It is well-structured and front-loaded with the main idea.

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?

The description covers purpose, contents, and behavior, but lacks parameter details. The output schema exists, so return values are handled, but the missing parameter semantics reduces completeness.

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 schema has 0% description coverage for the single parameter 'days'. The description does not explain this parameter at all, leaving the agent without guidance on how the argument affects the snapshot.

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 states it is a single call that gathers the usual starting point for diagnosis, listing specific components. It distinguishes itself from sibling tools by suggesting follow-up with specific tools for issues.

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?

It indicates use as a starting point and to follow up with specific tools, providing clear context. However, it does not explicitly state when not to use this tool or list alternatives.

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