get_sync_status

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

No annotations are provided, so the description carries the full burden of conveying that this is a safe read-only operation. The verb 'Get' makes the non-destructive nature clear, and the description discloses the specific data returned. It does not mention potential edge cases (e.g., behavior when sync is down), but for a zero-parameter getter 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 entire description is a single sentence that front-loads the tool's purpose and then lists the key output fields. Every word is informative, with no redundancy or filler.

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?

There is no output schema, so the description must communicate the return contents, which it does by listing cursor position, last sync time, and run counter. It is complete enough for a simple getter, though it could optionally clarify the response format or error handling.

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?

There are zero parameters, and the input schema is empty, so the baseline is 4. The description correctly avoids inventing parameter details and instead focuses on what the tool returns, which is appropriate.

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 uses a specific verb ('Get') and clearly identifies the resource ('health and status of the market sync system'), along with the specific data points (cursor position, last sync time, run counter). This distinguishes it from sibling tools like get_leaderboard or get_markets, which target different resources.

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 that this tool is used when the agent needs to check the sync system's health or status, providing clear context. However, it does not explicitly mention alternatives or exclusions, so it lacks the 'when-not-to-use' guidance that would earn a 5.

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