lc_list_sensor_download_targets

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

With no annotations, the description carries the full burden. It explicitly states the tool lists without downloading, making it clear it is a non-destructive read operation. However, it does not disclose whether the tool requires authentication or any other behavioral nuance, though for a zero-parameter list tool, this is acceptable.

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, concise sentence that directly states the tool's purpose and constraint. No unnecessary words.

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 the tool has no parameters and no output schema, the description is mostly sufficient. It clearly states what the tool lists. However, it could be enhanced by mentioning the output format (e.g., 'returns a list of URLs') or noting that it lists all available download targets.

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 no parameters, so schema coverage is perfect at 100%. The description adds meaning by specifying what is being listed (sensor installer target URLs). There is no need to document parameters.

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 states the tool lists supported sensor installer target URLs without downloading binaries. It specifies the verb 'List', the resource 'supported sensor installer target URLs', and the constraint 'without downloading'. It distinguishes from siblings like lc_list_adapter_download_targets by focusing on sensors.

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 implies the tool is for listing URLs only and not for downloading, but it does not explicitly state when to use this tool vs alternatives like lc_list_adapter_download_targets. No usage context or exclusions are provided.

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