start_downlink_simple

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully discloses a precondition (active satellite pass), but it does not describe what happens if the precondition is not met, whether a session can be started when one is already active, or other side effects of starting the downlink session.

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 two concise sentences, front-loaded with the core action and immediately followed by the key precondition. Every sentence earns its place with no redundancy.

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 no-argument, simple start action, the description covers the essential information: what the tool does and when it must be called. It is complete enough to invoke correctly, though it omits minor behavioral details like failure behavior if no satellite pass is active.

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 schema has zero parameters and the description reinforces that by explicitly stating 'no arguments required' and 'default parameters.' With no parameters, the baseline is 4, and the description adds helpful confirmation that no input is needed.

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 states a specific verb and resource: 'Start a data downlink session.' It clearly distinguishes this from the sibling stop_downlink_simple and other non-downlink tools, so an agent can identify its purpose immediately.

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 a clear usage context: 'Must be called during an active satellite pass.' It does not explicitly discuss when not to use it or name alternative tools, but for a simple start action the precondition is sufficient guidance.

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