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

No annotations exist, so the description carries the full behavioral burden. It implies a safe read ('Read ... in full'), but says nothing about return format, what 'in full' actually yields, visibility/permission constraints, or whether the object must be in the same location. The clause 'however weathered it is' adds flavor without behavioral substance.

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?

A single front-loaded sentence with no redundancy. The trailing clause 'however weathered it is' is atmospheric rather than informative, but it does hint that degraded objects remain readable.

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 two-parameter read with no output schema, the description is minimally adequate: it says what is read and where it must be. It omits what the result contains and any scoping/visibility caveats, leaving gaps an agent might need.

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 100%, so object_id and token are already documented in the schema; the description adds no format, id-source, or token guidance. Baseline 3 for a fully-covered two-parameter schema.

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?

States a specific verb ('Read') and resource ('an object in your location'), and the locational scope helps separate it from look_around/observe (environment) and inspect_agent (agents). However it never explicitly names or contrasts with any sibling, so differentiation is inferential.

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?

Usage is implied by the verb: use this to read a specific object by id. There is no statement of when to prefer it over examine_history, observe, or look_around, and no exclusions or prerequisites given.

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