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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description does add that the payload includes documentation, scope, selection policy and original source citations, which is useful content context, but it says nothing about behavior when the id is unknown or how language selection affects results.

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?

One short sentence with no filler, which is good, but the space is spent enumerating return fields rather than stating purpose or usage. The reader finishes the sentence without knowing the object's identity, so brevity comes at the cost of clarity.

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?

With no output schema, the description correctly takes on the job of previewing the returned content — dimension, measurement scope, selection policy, sources — which is the most valuable thing it could add for a read tool. It is only incomplete on the id and lang parameters and on sibling differentiation, which are secondary for a simple two-parameter lookup.

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% across two parameters, so the description carries the full burden and fails to meet it. It never explains what an "id" identifies, what format or namespace it belongs to (max length 80 is the only hint), or what the lang enum does to the returned documentation and sources.

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?

"Get" plus a list of returned content (dimension, measurement scope, selection policy, sources) gestures at the resource, but never says what an "object" actually is in this domain or what a caller would retrieve one for. It gives no signal that distinguishes it from siblings compare_objects and search_objects, so the agent must infer that this is the single-item retrieval path.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when to prefer search_objects or compare_objects. The only implied usage is "call with an id," which the schema already dictates, so the description contributes nothing to routing.

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