Trigger Import Source

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

Annotations already declare openWorldHint=true (external RSS fetch) and destructiveHint=false, so the safety profile is covered. The description adds that this is an on-demand execution, but does not disclose whether the run is synchronous or returns a job handle, nor whether concurrent runs are allowed — meaningful gaps for a trigger tool.

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?

A single front-loaded sentence with no filler. Every word contributes to identifying the action, the target and the timing behavior.

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 one-parameter trigger the description is workable, but it omits the follow-up path an agent needs — there is no output schema, yet it never says whether a job is created or that get_import_job/list_import_jobs should be used to track the run.

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% for the single 'id' parameter, so the schema already carries the semantics. The description adds no format, allowed value, or lookup guidance beyond it; baseline 3 applies.

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?

States a specific verb (trigger) plus resource (RSS import source) and qualifies the outcome (run immediately), which cleanly separates it from the list_/create_/update_/delete_import_source siblings. An agent can identify what this does without consulting the schema.

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 word 'manually' implies the intended case: forcing an immediate run instead of waiting for the scheduled cadence. However, it never names alternatives, states prerequisites (e.g. whether the source must be enabled or idle), or warns about repeat invocation, so usage is only implied.

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