download_portal_sources

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

No annotations are provided, and the description offers no behavioral details such as safety, side effects, or prerequisites. It only states the broad purpose, insufficient for an agent to understand implications.

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 extremely short but the second sentence is fragmented ('widget_ids=one widget.'), which harms clarity. It is concise but not well-structured, lacking complete sentences.

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?

Given 14 parameters, low schema coverage, no output schema, and no annotations, the description is grossly inadequate. It provides almost no context for correct use, leaving the agent to guess.

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 only 36%, and the description adds no parameter explanations beyond the schema itself. The schema descriptions are also minimal, leaving many parameters (e.g., incremental, max_widgets) unexplained in context.

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 clearly indicates the tool targets portal widgets/providers and contrasts with download_app_sources for whole apps, implying a focused download. However, it does not explicitly state the action 'download' beyond the name.

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?

The description provides implicit guidance by mentioning 'Whole app: download_app_sources' and 'widget_ids=one widget', suggesting use for targeted downloads, but lacks explicit when/when-not or alternatives.

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