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

No annotations are provided, so the description carries the full behavioral burden. The "[inference]" tag hints that this is a model-inference call (implying cost/latency), but nothing states summary length, style (extractive vs abstractive), language handling, or what the caller receives back. For a zero-annotation tool this is a significant 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?

The description is a single short fragment with no wasted words and no burying of key information. It is under-specified rather than poorly structured, which keeps it from a higher score but also avoids bloat.

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 one-parameter tool the burden is modest, but with no output schema the description should at least indicate the form of the returned summary (length, format, single vs multi-paragraph). It says nothing about inputs or outputs beyond the tool's name.

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?

There is one parameter (text) with 0% schema description coverage, and the description adds nothing about it — no size limits, language expectations, or formatting notes. The schema provides only an example string, so the description fails to compensate for the coverage gap.

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?

"[inference] Text summarization" identifies the resource (text) and the operation (summarize), so an agent can guess the basic intent. However, it largely restates the tool name and offers no differentiation from the nearby text_keywords and text_sentiment siblings. Purpose is inferable but not sharpened.

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?

No guidance on when to use this versus alternatives such as text_keywords, text_sentiment, or rag_augment, and no mention of prerequisites or context. The agent is left to infer usage entirely from the name.

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