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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds no behavioral context beyond that — nothing about what the returned 'contracts' mean, freshness, permissions, or error behavior for an unknown domain_id.

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 filler. It is efficient, though the terseness comes at the cost of the missing detail noted elsewhere.

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?

An output schema exists so return values need not be spelled out, but the description still omits how to source domain_id and how this tool fits alongside the many sibling knowledge tools. For a tool whose only parameter is opaque, this is not enough.

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 the single required domain_id parameter has no prose explanation. The description does not state the expected slug format (only the schema pattern hints at it) nor that the id comes from list_knowledge_domains, so it fails to compensate for the coverage gap.

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 gives a verb ('Return') and a resource ('context and public-record contracts for one installed knowledge domain'), which is enough to understand it retrieves metadata about a single domain. However, 'context and public-record contracts' is jargon that does not clearly convey what is actually returned, and it never distinguishes itself from siblings like list_knowledge_domains or query_domain_knowledge.

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 and no mention of alternatives. The agent is not told to call list_knowledge_domains first to obtain a domain_id, nor how this differs from query_domain_knowledge or get_knowledge_provenance.

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