get_source_observation

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

No annotations are provided, so the description carries the full burden. It adds useful behavioral context: the observation is immutable, the retrieval is exact, and the response includes the verified raw payload. It does not explicitly state read-only, but the verb 'Retrieve' makes that clear.

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 front-loaded sentence with no filler. It communicates the action, the exactness, the immutability, and the payload content efficiently.

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 one-parameter lookup with an output schema, the description covers the core semantics adequately. It lacks guidance on when this tool should be chosen over sibling tools, which prevents a perfect score, but nothing critical is missing for invoking it correctly.

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 provides only a parameter name and no description (0% coverage), so the description must compensate. The phrase 'by ID' tells the agent that observation_id is the identifier, but it provides no format, origin, or additional constraints beyond the schema's required flag.

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 is specific: 'Retrieve one exact immutable source observation by ID' names the verb, the resource, and the lookup key, and adds 'including verified raw payload' to clarify what is returned. It does not explicitly differentiate from sibling tools like get_vehicle_revision, but the resource is distinct enough to be clear.

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 this tool is for retrieving a single known observation by its ID, but it never states when to prefer it over siblings such as get_vehicle_history or get_vehicle_revision, nor does it mention any exclusions or alternative conditions.

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