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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds useful behavioral context beyond the annotations: drafts are excluded from results, and the full set of status values is enumerated. It does not address the annotation's destructiveHint=true, leaving that inconsistency unresolved.

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 compact and front-loaded: the core list behavior and returned fields come first, followed by the draft exclusion and status values. Every sentence adds information without padding.

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 correctly names the returned fields, and it explains the draft omission and status values. The only noticeable gap is that it does not clarify pagination or ordering, and it leaves the annotation's destructiveHint=true 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 100%, so the baseline is 3, but the description adds meaning by enumerating the allowed status values (idea, brief, draft, review, published, archived) even though the schema has no enum. It does not add further detail beyond what the schema provides for site_id.

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 resource and scope: all content briefs for a site, along with the fields returned. It also distinguishes itself from the sibling tool by noting that drafts are omitted and directing the agent to get_content_brief.

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?

Provides an explicit alternative for the one important exclusion: drafts are omitted, so use get_content_brief. It does not spell out broader when-to-use guidance versus unrelated sibling tools, but for this straightforward list operation the key routing condition is present.

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