h1_get_report

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'Get a report with its relationships' without explaining what relationships are returned, whether the operation is read-only, or any other behavior. This is inadequate for a tool with no structured metadata.

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 one concise sentence and is front-loaded with the verb and resource. It does not contain wasted words, though 'with its relationships' is vague but still compact.

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 the absence of annotations and output schema, the description is too minimal. The term 'relationships' is ambiguous and could be critical for the agent to understand what will be returned. A simple get tool still needs to clarify its scope to be effective.

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 input schema fully describes the only parameter 'report_id' as 'Report ID' (100% coverage). The description adds no additional meaning beyond the schema. For a single required parameter with full schema coverage, the baseline of 3 applies.

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 the verb 'Get' and the resource 'report', which is clear at a high level. However, 'with its relationships' is vague and does not specify what relationships are included (e.g., attachments, signals, weaknesses), nor does it distinguish this from siblings like h1_get_report_intent or h1_list_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?

There is no guidance on when to use this tool versus alternatives such as h1_list_reports for many reports or h1_get_report_intent for report intents. The description provides no context, prerequisites, or exclusions.

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