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

Adds real behavior beyond the annotations: it runs asynchronously in the background, is triggered automatically every 14 days and on profile save, is incremental/cheap, and — critically — the returned summary is from the LAST crawl, not the current one, so the agent must poll again. That staleness caveat and the cost model are exactly what an agent needs and nothing in the structured fields conveys them.

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?

Four sentences, each carrying distinct information (what, when-it-runs-automatically, cost profile, return and polling loop), with the primary action front-loaded. Slightly dense in clause count but no genuinely wasted sentence.

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, the description carries the return-value burden well (whether there was anything to read, last crawl summary with pages/UUIDs/passages) and explains the async polling loop. It only falls short on the workspaceId parameter and on how this interacts with sibling knowledge tools.

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?

The description never mentions workspaceId or idempotencyKey. With schema coverage at only 50%, the undocumented workspaceId is left entirely to inference, and the description does not compensate for that gap even though it is the one parameter that scopes the call.

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?

Names a specific action (re-read) on a specific resource (the workspace's brand profile websites plus social-account style) and states the goal (Sparky answers with what the site says today). This is clearly separable from siblings like learn_brand_style, teach_knowledge, search_knowledge and get_brand_memory.

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?

It gives the condition that selects this tool ('now' versus the automatic runs every 14 days and on profile save) and tells the agent the correct next step after calling ('call it again in a minute or two'). It never contrasts itself against the knowledge siblings (teach_knowledge / learn_brand_style), so routing guidance is strong but not exhaustive.

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