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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description still adds real value beyond them: omitting space_id does not create a space, and the returned instructions cannot expand task grants or spending — a security-relevant constraint an agent wouldn't infer from the 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?

Two dense sentences with the resource and return content front-loaded, then the space_id fallback, then the safety caveat. Every clause carries information, though the grants/spending sentence is a non-sequitur in placement relative to the read operation.

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 shape needs no explanation, and annotations cover safety. What's missing is the behavior of the uncharted content_sha256 parameter — a read tool with a hash argument implies version pinning or concurrency control that the description never explains.

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%, so the description must compensate and it only partly does. It explains the space_id omission semantics well and implies knowledge_id identifies the entry, but content_sha256 is only alluded to as 'with its hash' and it is never stated whether it is an input precondition, nor what happens on mismatch.

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 the exact SKILL.md of a current private knowledge entry, returning it with its hash. That is concrete enough to act on, but it doesn't distinguish this from private_knowledge_get or get_skill, which an agent could easily confuse with it.

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?

Names an explicit alternative and the condition that selects it: an omitted space_id reads existing Personal without creating it, and private_space_personal exists for explicit first-use setup. It gives no guidance on when to prefer this over private_knowledge_get or get_skill, so the routing is only partly covered.

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