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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the returned field set and the fact that an offer or position is fetched in full, but it does not disclose error behavior, ID provenance, or other operational details; 'Read-only' merely repeats the annotations.

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 main sentence is front-loaded with the operation and scope, followed by a useful enumeration of returned fields. The trailing 'Read-only' is redundant given the annotations, but the overall description is compact and easy to scan.

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 single-record read tool with one parameter, the description is largely complete because it identifies the resource, the lookup key, and the returned fields in the absence of an output schema. Minor gaps remain around not-found behavior and where the id comes from, but the core usage context is present.

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?

Schema description coverage is 0%, so the description needs to compensate for the undocumented id parameter. It says 'by its id' and implies the id may refer to an offer or position, but it does not explain the required numeric format, where to obtain the id, or any distinction between offer ids and position ids.

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 a specific retrieval operation: one offer or position in full by its id, and enumerates the returned fields. It is specific enough to distinguish a single-record fetch from a list or action, but it does not explicitly differentiate itself from siblings such as explain_offer or find_offers.

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 the tool is used when the caller already knows a specific offer or position id. However, it gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives for searching or explaining offers.

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