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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing: no side effects, no auth or permission requirements, no rate limits, no return shape. Calling it a "pipeline" adds no actionable information.

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?

One short sentence with no padding, but brevity here reflects under-specification rather than efficiency. There is no front-loaded statement of what the tool returns or when to call it.

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 annotations, no output schema, and a description that gives no information about the fetched resource, its format, or the purpose of the notification_message fallback. An agent has essentially nothing to act on beyond the tool 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?

Schema description coverage is 100%, so the single notification_message parameter is fully documented in the schema, establishing the baseline of 3. The description adds nothing about it, and notably does not explain why a fetch operation takes a user-facing failure message.

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?

"Run the fetch_external_resource_file pipeline" restates the tool name as a pipeline invocation without saying what is actually fetched, from where, or what the result represents. It is effectively a tautology, though the name itself hints at fetching an external resource file.

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 when-to-use guidance, no exclusions, and no mention of the many sibling fetch_* tools (fetch_resource, fetch_user_profile_picture, etc.). An agent cannot tell from this text when to pick this tool over fetch_resource.

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