carapace_get

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'Retrieve' (read-only) but does not mention what happens when the ID is not found, authentication requirements, or the structure of the returned insight. This is a significant gap for a tool with no 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 that front-loads the verb 'Retrieve' and clearly states the resource and qualifier. Every word earns its place, making it highly efficient.

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 simple get-by-ID tool with a single parameter and no output schema, the description is adequate but lacks detail about the return format or error behavior. It does not specify what happens for non-existent IDs, and since there is no output schema, the agent might need more context about the response shape.

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 schema covers 100% of the single parameter 'id' with the description 'The contribution ID to retrieve', so the baseline is 3. The tool description adds no additional meaning beyond echoing the schema's 'by its ID'. No extra syntax or semantics are provided.

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 clearly states the tool retrieves a specific insight by its ID, with the verb 'Retrieve' and resource 'specific insight from Carapace AI'. This distinguishes it from siblings like carapace_query (likely listing/search) and carapace_contribute/update/delete (write operations).

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 'by its ID' implies this tool is for when you have a specific ID and want that single insight, but there is no explicit guidance on when to prefer this over carapace_query or any alternatives. Usage is only implied, not stated.

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