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

Adds behavioral context beyond annotations: lists the returned fields (id, score, title, status, source), describes filtering behavior, and states the default page size (25). Annotations already cover readOnly, idempotent, and safe operation, so this extra return-field info is a valuable addition.

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?

Three concise sentences that front-load the primary use case, then return fields, then an exclusion. Efficient with no wasteful repetition.

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?

Though an output schema exists, the description lists key return fields which helps confirm expectations. It covers usage, return content, filtering, pagination default, and exclusions, leaving no significant gap for this read-only listing tool.

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 schema fully documents each parameter's meaning and constraints. The description mentions filtering by status or minimum score, which maps to existing parameters but adds no new syntax or detail beyond the schema.

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 (list) and resource (saved topic ideas) and explicitly excludes fetching new ideas, distinguishing it from the sibling refresh_topic_ideas.

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 a clear usage scenario ('when someone asks what they could write about next from topic ideas already saved') and names an exclusion ('Not for fetching new ideas'), routing the agent to the refresh alternative. No further alternatives are named.

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