GetValueMetadata

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

With no annotations provided, the description carries the full burden, and it does disclose a meaningful behavioral trait: the tool avoids fetching the full value. It also enumerates the returned metadata categories (state, type, dependencies, dependents), giving the agent a concrete expectation of behavior beyond the tool name.

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, well-structured sentence that front-loads the core action and resource, then efficiently lists the metadata contents and the key non-fetching behavior. There is no redundant or vague wording.

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?

The description adequately covers what the tool returns and its key non-behavior, and the input schema fully documents parameters and the notebook selection mechanism. It does not describe edge cases like missing values or timeout behavior, but for a metadata retrieval tool the description is sufficiently complete for an agent to invoke 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?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds no additional parameter-specific semantics beyond the overall value metadata context, which matches the baseline of 3 for high schema coverage.

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 identifies a specific verb ('Get metadata'), a specific resource ('a value in the Observable runtime'), and the exact scope of that metadata ('state, type, dependencies (inputs), and dependents (outputs)'). It also differentiates itself from GetValue/GetValues by adding 'without fetching the full value.'

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 'without fetching the full value' provides clear contextual guidance: use this tool when you only need metadata rather than the complete value. It stops short of explicitly naming alternatives such as GetValue or GetDependencyGraph or stating when not to use it, so it does not reach a 5.

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