metadata_get

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

"Side-effects: None. Read-only metadata query" simply restates the readOnlyHint annotation that the agent already has, so it adds no behavioral context. Nothing is said about behavior for an unknown namespace, whether a namespace must be written first via metadata_set, or any native-bridge failure modes.

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?

Front-loads the purpose in one sentence and keeps the rest short. The side-effects sentence is largely redundant with the annotation, a small amount of wasted space.

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?

Annotations carry the safety profile, the schema fully documents both params, and an output schema exists, so return values need not be described. What is missing is only edge-case behavior (missing namespace, namespace scope per PID), which is modest given the supporting structure.

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 coverage is 100%, so both parameters are already documented in the schema; baseline 3 applies. The description echoes the "schema-agnostic namespace" and "persistent semantic PID" wording but contributes no extra format or constraint detail.

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 and resource: reading one metadata namespace for a persistent semantic PID. The disambiguation line hints at the difference from metadata_query/metadata_set, but never names those siblings, so the agent must infer the boundary.

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?

"Use to retrieve engineering attributes attached to entities" implies when to reach for it, but there is no explicit when-not condition and the obvious alternatives (metadata_query, metadata_set) are not named. Usage is inferable rather than stated.

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