getJsonReport

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

With no annotations provided, the description bears full burden for behavioral transparency. It states 'generate and retrieve' but does not clarify if the report is generated on-demand or pre-existing, nor does it disclose potential side effects, required permissions, or error conditions. The phrase 'Generate and retrieve' is ambiguous and could imply both creation and retrieval.

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 two sentences, front-loading the core purpose and listing content types. Every sentence adds value without redundancy. It is concise and well-structured.

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 many sibling tools, the description is minimally complete for a simple retrieval tool. It covers the report content but lacks guidance on alternative tool usage (e.g., getJsonReportSection) and return format details. It is adequate but not comprehensive.

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?

Schema coverage is 100% with a single 'hash' parameter described as 'Hash file to getting scan logs'. The description adds no further meaning beyond the schema, such as accepted hash formats, origin, or examples. Baseline score of 3 is appropriate for full coverage but no added value.

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 generates and retrieves a comprehensive JSON security report for a scanned mobile application, using specific verbs 'generate and retrieve' and identifying the resource as a JSON report. It distinguishes itself from sibling tools like getJsonReportSection (which retrieves specific sections) and generatePdfReport (PDF format).

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 mentions the report includes detailed findings, but does not explicitly guide when to use this full report versus the many available section tools (e.g., getJsonReportSection). No exclusions or context about prerequisites (e.g., scan must be complete) are provided, leaving implicit usage guidance.

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