get_sync_logs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns connection state including sync history and warnings, but does not disclose potential side effects (though 'Get' implies read-only), error behavior, rate limits, or data format. The description is minimal and does not add meaningful context beyond what the name suggests.

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 sentences, with the primary action front-loaded: 'Get sync logs for a connection.' The second sentence adds the return content. There is no extraneous information or redundancy, making it appropriately concise and well-structured.

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?

The tool is simple with one parameter and no output schema or annotations. The description covers the basic purpose and return content, but lacks details on the nature of the logs (e.g., chronological order, pagination, error handling) and any prerequisites. For a tool of this complexity, it is minimally viable but leaves room for additional context.

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 input schema has 100% coverage with the parameter description 'The connection ID.' The tool description does not add further meaning beyond referencing 'a connection.' Since the schema already documents the parameter well, the description adds no additional semantic value, matching the baseline for high schema coverage.

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+resource combination: "Get sync logs for a connection." It clearly identifies what the tool does and what it returns (connection state, sync history, warnings). While it doesn't explicitly distinguish from siblings like get_sync_status, the mention of "sync history and warnings" implies a more detailed output than a basic status tool, giving it reasonable purpose clarity.

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 like get_sync_status. It does not specify scenarios (e.g., troubleshooting sync issues, reviewing past runs) or state when not to use it. The usage context is only implied by the tool name and description, leaving the agent to infer suitability.

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