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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond annotations by stating that only released, non-revoked reports are returned and that pending review material and access credentials are never returned. This helps the agent set correct expectations about response content.

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 short sentences with no wasted wording. The core purpose is stated first, followed by a valuable exclusion clause. Every sentence earns its place.

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 simple two-parameter getter with strong annotations, the description covers the essential retrieval scope and content exclusions. It does not describe return fields or error behavior, but the absence of an output schema and the tool's simplicity make the description sufficiently complete for correct invocation.

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 description coverage is only 50%: workspaceSlug is documented, but reportId only has length constraints and no semantic explanation. The description does not compensate by explaining how reportId is structured, obtained, or used to select a specific report.

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 states a specific verb and resource: 'Return one released, non-revoked workspace report.' It clearly differentiates this single-report getter from sibling tools like list_reports and get_finding. The qualifiers 'released' and 'non-revoked' add precise scope.

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 conveys that this is for retrieving a single released report and that pending or sensitive material will not be returned. It does not explicitly mention when to prefer list_reports or other alternatives, but the single-item and status constraints give clear contextual guidance.

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