get_sync_status

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's assurance that it 'never starts import or paid inference' mostly reinforces known safety properties with useful specificity about cost and side effects. However, it does not disclose the return shape, freshness, or what 'sync status' means beyond counts.

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 definition is a single compact sentence with the core action front-loaded and no wasted clauses. The semicolon-separated caveat is concise, though the phrase 'this MCP tool' adds little.

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?

With zero parameters, no output schema, and rich annotations, the description is nearly sufficient but omits what the returned counts represent and what the sync status conveys. For a status-reading tool, that leaves a meaningful gap in understanding the response.

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 takes zero parameters, so there is no parameter semantics burden and the baseline is 4. The description adds nothing needed beyond the schema, which is appropriate here.

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 verb and resource ('Read memory counts'), which is clearer than a tautology, but 'memory counts' is vague for a tool named get_sync_status and does not clarify what counts or status are returned. It also does not differentiate its role from siblings such as get_facts or search_memory.

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 negative clause 'never starts import or paid inference' implicitly signals a safe status-check use case, but no explicit when-to-use guidance or alternatives (e.g., get_context_brief, search_memory) are named. The agent must infer selection from the name and the exclusion alone.

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