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

Annotations only cover readOnlyHint and openWorldHint, but the description adds substantial behavior: a 20 KB byte budget with truncatedPaths reporting elision, _hidden: true marking of private keys that are hidden from SDK clients but not the dashboard, contentHash as a version token for optimistic concurrency, and deepLinkPath as a shareable ?path= fragment. These are exactly the operational facts an agent needs and none are inferable from annotations.

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?

Purpose is front-loaded in the first sentence and subsequent sentences cover modes, truncation recovery, hidden keys, versioning, and documentation fields in a logical order. It is dense and mostly earns its length, though the deepLinkPath and description/keyDescriptions sentences could be tightened slightly.

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 and six parameters, the description proactively explains the response payload surface (truncatedPaths, _hidden, contentHash, deepLinkPath, description/keyDescriptions) so the agent can act on the result without a return-type spec. Nothing material for a correct call is missing.

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 the baseline is 3; the description nevertheless adds cross-parameter meaning the schema lacks — that 'path' is a key array used specifically to drill into truncatedPaths, and that 'structure' is the default mode while 'values' is budget-bound. It does not restate depth semantics in more detail than the schema, so a 4 rather than 5.

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 ('Read a configuration by id') and immediately distinguishes the operation from sibling reads (list_configurations, search_configuration) and writes (update_configuration) by describing the two read modes and their cost/safety tradeoff.

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?

Explicitly routes the agent: mode 'structure' is default and cheap/safe at root, mode 'values' is for actual values, and when output is truncated the agent should re-call with 'path' set to a truncatedPaths entry. It also names the follow-up tool (update_configuration_descriptions) for editing docs, leaving nothing to inference.

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