propagate_orbit_j2

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

With no annotations, the description is responsible for all behavioral disclosure. It mentions numerical integration and J2 perturbations, and notes that errors are returned as strings rather than exceptions. However, it omits any discussion of side effects, performance, or required permissions, leaving gaps.

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 concise and well-structured with Args and Returns sections. Every sentence contributes useful information, and the front-loading of the purpose sentence makes it immediately clear what the tool does.

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 that an output schema exists, the description need not detail return values. It covers the three parameters adequately and mentions error handling. For a moderately complex orbital propagation tool, the description provides sufficient context for an AI agent to use it correctly, though more detail on initial state format would improve completeness.

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 0%, so the description must compensate. It lists the three parameters with brief explanations (e.g., 'Initial orbital state (elements or state vector)') which adds meaning beyond the parameter names. However, it does not specify the expected format of the initial_state object or any constraints on the time step.

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's purpose: propagate orbit with J2 perturbations via numerical integration. The verb 'propagate' and resource 'orbit' are specific, and the mention of 'J2 perturbations' distinguishes it from other orbital tools on the server.

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 no guidance on when to use this tool versus alternatives. It lists arguments but does not specify scenarios, prerequisites, or cases where other tools (e.g., hohmann_transfer) would be more appropriate.

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