sync_peers

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

Annotations already declare readOnlyHint=true, and the description's 'List' matches that read-only safety profile. The description adds one useful context detail, that the peers are configured via THREADKEEPER_SYNC_PEERS, but it does not describe response behavior, error cases, or side effects.

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 part—verb, resource, and configuration source—carries meaning.

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 zero-parameter, read-only tool with an output schema, the description is sufficient to invoke correctly. It is less complete on choosing this tool over nearby siblings, but that gap is already captured in usage guidelines.

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 zero parameters and an empty input schema, so no parameter documentation is necessary. The description's mention of THREADKEEPER_SYNC_PEERS is the only relevant context and it is sufficient.

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 ('List') and resource ('configured sync peers') and identifies the configuration source (THREADKEEPER_SYNC_PEERS), so an agent can tell what the tool returns. It does not explicitly name a sibling alternative such as 'peers' or 'sync_status', so sibling differentiation is weaker than ideal.

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 phrase 'List the configured sync peers' implies the tool is for inspecting configured peers, which gives some contextual cue. However, it provides no explicit when-to-use or when-not-to-use guidance and does not contrast with sibling tools like 'peers' or 'sync_status'.

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