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

With no annotations, the description carries the full burden and does well: it discloses the cost (5 credits per call), the external OpenAI dependency, and that historical top-performing posts are retrieved as context. It doesn't cover latency, failure behavior when no historical data exists, or whether results are cached/persisted.

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 tight sentences with zero filler: purpose, mechanism/output, cost, then parameter routing. The most decision-relevant facts (what it produces, what it costs) are front-loaded.

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?

Covers cost, mechanism, and scoping for a 3-parameter tool with no output schema. The return shape is only described as "5 concrete angles" -- whether that is plain strings or structured objects isn't clear, which matters some given no output schema exists.

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 coverage is 100%, so baseline is 3; the description adds genuine meaning by spelling out the alternative scoping modes and the default when neither ID is supplied, which the schema's per-field descriptions don't establish. It stops short of clarifying whether both IDs may be passed simultaneously.

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 ("suggest distinct content angles" for a topic) plus the quantity produced (5) and the data basis (top-performing historical posts). It is clearly distinguishable from sibling readers like get_topic_insights or find_similar_posts, which don't generate new angles.

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?

Explicitly explains the scoping decision: use profile_id for a tracked profile, collection_id for a collection, or neither for the full library. It doesn't state when to prefer this over adjacent tools (e.g., get_topic_insights) or when not to call it, so not a 5.

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