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

Beyond the readOnlyHint annotation, the description discloses that the tool is FREE, lists the content of the workspace, and explains the meaning of enabled:false—that the space has no content engine yet. This gives the agent actionable behavioral knowledge about how to interpret the response.

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 description is three sentences with no filler: it front-loads the return contents, then adds the FREE signal and usage guidance, then the key enabled:false branch. Every sentence earns its place.

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?

For a simple single-parameter read tool with no output schema, the description is complete: it tells the agent what data will come back, when to retrieve it, and how to interpret the critical enabled flag. No essential behavior 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 description coverage is 100%, and the single parameter space_id is already documented as coming from list_content_spaces or any Amplify space the user owns. The description adds context about the workspace contents but does not need to add parameter-level detail. Baseline 3 is appropriate.

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 opens by naming exactly what the tool returns: the brand's voice, platforms, post types, playbook, review threshold, topic inventory, and style guides for one content space. This clearly distinguishes it from siblings like list_content_spaces (listing spaces) and setup_content_space (creating/updating a space).

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?

The description explicitly says to read this BEFORE writing any draft and at the start of any content conversation. It also provides a conditional follow-up: if enabled:false, offer setup_content_space, which tells the agent when not to proceed with writing and what sibling to invoke instead.

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