netintel_text_summarize

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

With no annotations, the description carries the full disclosure burden, and it does add real behavioral context: the backing model (Claude Haiku), that URLs are fetched and extracted, and that an input cap is enforced. However, it never states the cap value, what happens on fetch failure, or whether url and text are mutually exclusive — significant gaps for a 0-required-param tool.

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 core capability is front-loaded and the dash-separated clauses are information-dense, but the text is truncated mid-sentence ("so agents can…"), leaving an unresolved clause that consumes space without delivering content.

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?

There is no output schema and no annotations to fall back on, yet the description is cut off and omits how the summary is structured, how many bullet points default, and how the two input modes interact. For a tool with three undocumented parameters and zero required fields, an agent cannot confidently construct a call from this alone.

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% across 3 parameters, so the description must compensate and only partially does. "Raw text or a URL (which it fetches and extracts)" covers url and text loosely, but max_points is never mentioned and neither the url/text exclusivity nor the units/limits of max_points are clarified.

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 and resource ("Summarize any text or web page") plus the output shape (concise summary plus key bullet points), which is far more than a restatement of the name. It does not explicitly distinguish itself from near-neighbors like netintel_page_extract, netintel_extract, or netintel_classify, so the agent must infer the boundary.

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 is only implied through the input modalities ("accepts raw text or a URL"), which suggests when the tool is applicable. There is no statement of when to prefer it over netintel_page_extract/page_extract for fetching, or entity_extract/classify for other text tasks, and no exclusions or prerequisites.

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