implicit_inspect_state

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description adds meaningful value beyond them: it clarifies that no materialization side effect occurs and that the return is retained serialized bytes rather than live RAM handles. It stops short of describing pagination or size limits.

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?

Three short sentences, front-loaded with the verb and resource, and nothing is padded. Density of jargon ('materialized', 'retained serialized bytes') slightly limits immediate comprehension but every sentence carries information.

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?

Return semantics and the no-load guarantee are well covered for a read-only inspection tool with no output schema, and annotations carry the safety profile. The gap is parameter documentation: with 0% schema coverage, the description should have said what coordinate and universe_id denote.

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% and neither parameter is explained in the description. The phrase 'addressed experience' loosely gestures at 'coordinate', but universe_id and coordinate formats/ranges are left entirely to the schema's type and pattern constraints, so an agent gets no semantic guidance.

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 (materialized resource metadata) scoped to 'an addressed experience', which separates it from implicit_create_universe and implicit_materialize. It does not explicitly name how it differs from the close sibling implicit_inspect_universe, so an agent must infer the universe-vs-state distinction.

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?

'Does not load missing resources' is a partial when-not constraint, implying implicit_materialize must run first for un-materialized targets. However, no alternative tool is named and no explicit condition for choosing this over implicit_inspect_universe or implicit_get_provenance is given.

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