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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing what the call actually returns (limits, rules, a fill-in voice guide) and that the guide is something the caller must complete. It stops short of noting any auth or error behavior, which keeps it out of the top band.

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 sentences with zero filler — the positive use case is front-loaded and the exclusion follows. Every clause 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?

It is adequate for a small read-only tool with only two parameters, and it does describe the return content since no output schema exists. However, the unexplained goal parameter and the lack of any shape for the returned brief leave real gaps for a tool whose whole purpose is producing a template.

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 needs to carry parameter meaning. It hints at the required platform parameter through "platform limits" but never says what the goal parameter is for or how it shapes the brief, leaving half the input undocumented in both schema and description.

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 (get writing brief) and enumerates the payload: platform limits, writing rules, and a voice guide template. It also explicitly separates this tool from read_posts, so an agent can tell the two apart without opening either 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?

Gives a positive trigger ("before writing new drafts") and an explicit exclusion ("Not needed to read posts or build a voice guide from them"), naming the alternative read_posts that covers that case. Nothing about when to reach for this tool is left to inference.

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