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

Annotations declare readOnly=false, destructive=false, idempotent=true, openWorld=false, and the description adds substantial context beyond them: the consent gate, the eligibility boundary, and the prohibition on raw transcripts or historical-conversation data. No contradictions with annotations; the write-without-destruction profile is consistent.

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?

The core action is front-loaded in the first clause, and each subsequent sentence adds a distinct constraint rather than restating. It is dense but nearly every clause earns its place; a light structural break between consent rules and scope rules would improve scanability.

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 no explanation, and the consent/eligibility rules are unusually thorough for a mutation tool. The remaining gap is that the provenance/request_id/provider envelope, which is non-trivial given the nested schema, goes unexplained.

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% for the four top-level required parameters, so the description bears the burden of explaining them. It clarifies knowledge_scope (already a const in the schema) but says nothing about provider, request_id, or provenance, leaving half the top-level parameters semantically unexplained.

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 with precise scope: 'Create pending, user-owned general-knowledge card drafts.' This clearly distinguishes it from siblings like create_knowledge_bundle_drafts and validate_knowledge_bundle, and an agent can identify the operation without opening the schema.

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 defines the precondition ('only after clear affirmative consent'), enumerates ineligible categories (decisions, policies, preferences, plans, tasks, etc.), and clarifies that an assistant suggestion alone is not consent. It also names what the tool cannot do (approve, publish, modify public cards), effectively routing those intents elsewhere.

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