list_upload_targets

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds a useful behavioral constraint by stating that arbitrary filesystem browsing is never exposed, but it does not cover authentication, profile scoping, or result behavior.

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 definition is a single front-loaded sentence with no filler, and the security constraint is placed immediately after the core purpose. It is concise and efficient, though the phrase "native plugin import targets" is somewhat dense.

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 simple read-only list tool, the description is still under-specified: it does not explain the required profileId or how the returned targets relate to the nearby upload and import tools. Annotations and the schema provide some structure, but the description leaves important invocation context implicit.

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?

The tool has one required parameter, profileId, with 0% schema description coverage, and the description does not explain what profileId means or how it scopes the listed targets. The description therefore does not compensate for the missing parameter documentation.

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 has a clear verb ("List") and resource ("configured native plugin import targets"), and it clarifies that it does not expose arbitrary filesystem browsing. It does not explicitly distinguish itself from sibling tools such as inspect_upload_plugin, upload_media, or list_libraries.

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?

It offers no explicit guidance on when to use this tool versus alternatives. The phrase "never exposes arbitrary filesystem browsing" sets a safety boundary but does not tell an agent when this listing should be selected over inspect_upload_plugin or upload_media.

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