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

With no annotations supplied, the description carries the full burden and does well: it enumerates the three license_note policies and exactly what each returns, notes that include_body=false overrides even a full license, states body_policy is reported back, and documents the {error: "not_found"} case. It never states this is a read-only operation or discusses permissions, which is the remaining gap.

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 one-line purpose followed by clearly labeled gating rules, Args, and Returns. Every sentence carries information an agent needs to invoke the tool correctly; nothing is padding.

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?

An output schema exists, so the Returns section is partly redundant, yet it usefully flags the error shape and body_policy field. Combined with full parameter explanation and gating behavior, an agent has enough to call this correctly; only auth/permission context is absent.

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 0%, so the description must compensate, and it does: it gives an id format example ('news-20260702-4c769f') and explains include_body's exact effect including its interaction with license gating. It does not restate the boolean default, but the behavior is unambiguous.

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 opens with a specific verb+resource ('Fetch a full article by id'), which cleanly separates it from the listing/search siblings like portal_search and portal_list. It stops short of naming an alternative explicitly, but 'by id' versus search-style siblings is unambiguous.

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?

Usage context is clear from the Args section (call it when you have an article id) and from the license_note gating rules that govern what comes back. However, there is no explicit when-to-use/when-not guidance relative to portal_search or portal_get_agent_surface, so the agent must infer selection from name alone.

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