megalinter_parse_reports

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

No annotations are provided, so the description carries full burden. It only states the tool parses and returns structured data, without disclosing any behavioral traits like permissions needed, side effects, or performance implications. More transparency is needed for a parse operation.

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 sentence that conveys action and resource upfront. No redundant information. Every word adds value, making it highly efficient.

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 tool has two optional parameters and no output schema. The description states returns structured data but does not specify the format or structure of the output. Given the presence of sibling analysis tools, more detail on what 'structured report data' entails would improve 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?

Both parameters have descriptions in the input schema (100% coverage). The description does not add any extra meaning beyond what the schema provides, such as example values or format constraints. Baseline of 3 is appropriate.

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 the tool parses MegaLinter JSON or SARIF reports and returns structured data. It specifics the resource (reports) and action (parse), distinguishing it from siblings like 'megalinter_get_issue_summary' which likely summarize rather than parse raw reports.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for parsing reports, but does not mention when to choose JSON or SARIF, nor does it exclude specific contexts. This is adequate but lacks differentiation from other analysis tools.

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