ss_contact_get

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

Without annotations, the description carries the full burden. It correctly indicates a read operation (no side effects), but fails to disclose crucial behaviors such as response structure, error handling for missing contacts, or authentication requirements. This underdiscloses for a tool with zero annotation support.

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 a single, concise sentence with the key verb ('Read'), resource ('contact details'), and lookup criterion ('by contact ID'). No extraneous information, making it efficient for quick comprehension.

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 the lack of output schema and annotations, the description should explain what is returned (e.g., full contact object) or indicate typical response format. It only covers the input, leaving the agent without understanding of the tool's result. For a simple tool, this is insufficient.

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 provides full coverage (100%) with a clear description for the single parameter. The tool description adds no additional meaning or context beyond what the schema already conveys. Baseline 3 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 explicitly states the action 'Read' and the resource 'contact details', with a clear lookup method 'by contact ID'. This distinguishes it from sibling tools like ss_contact_save (write) and ss_contact_attr_get (attribute-specific).

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 usage for retrieving full contact details by ID, but it does not explicitly mention when to use vs. alternatives like ss_contact_attr_get for specific attributes. No guidance on prerequisites or excluded scenarios.

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