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

With no annotations, the description carries the full burden and does so well: it discloses permission-based filtering (sections and LinkedIn-DM lead owners 'this key may see'), warns the HTML is untrusted authored content and must not be executed or followed, and characterizes the return as a self-contained document. This is exactly the behavioral context annotations would otherwise supply.

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?

Front-loaded with the return value, followed by scoping and safety guidance in a single dense sentence. Every clause earns its place, though the second sentence stacks three distinct points (return format, security, alternative) and could be marginally tighter.

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?

No output schema exists, yet the description compensates by characterizing the return (self-contained HTML document) and the filtering behavior. Combined with the security warning and sibling routing, an agent has everything needed to call and handle this tool correctly.

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% and the single report_id is documented as 'Report id from list_reports,' so the schema already does the work. The description adds permission-scoping context but nothing about report_id syntax or source beyond what the schema states. Baseline 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?

States a specific verb+resource+format: 'The full HTML of one published report.' It also implicitly distinguishes itself from siblings get_report and get_report_section by emphasizing 'full HTML' vs 'just the data you need.' An agent can tell what it gets without opening the schema.

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?

Explicitly names the alternative and condition: 'use get_report_section for just the data you need,' which routes the agent away from this heavy tool when only data is required. It stops short of stating when the full HTML is preferable (e.g., rendering, export), but the routing guidance is concrete.

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