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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, whether results are paginated, how filters combine, what the response shape is, or whether any side effects occur. The description adds only a list of filter dimensions, not behavioral context.

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 a single sentence with no filler, and the key action and resource are front-loaded. It is appropriately concise, though it could earn a 5 by adding a brief usage condition or alternative reference without bloating.

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 six parameters, no annotations, no output schema, and 0% schema description coverage, the description is too thin. An agent cannot determine pagination behavior, filter combination rules, or what a 'curated content item' is in this context. The description is adequate only for a rough first-pass selection, not for reliable invocation.

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 must compensate for six undocumented parameters. It names four filter dimensions (feed ID, search, source scope, time range) but does not explain the 'limit' parameter or the 'team_id' parameter, and it does not clarify value formats or filter combination semantics. This is a partial compensation at best.

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?

The description states a specific verb ('Get') and resource ('curated content items'), and lists the available filter dimensions (feed ID, search, source scope, time range). It is clear enough to distinguish from siblings like list_listen_items or get_listen_item, though it doesn't explicitly name a sibling alternative.

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?

The description implies usage by listing filter options, but it does not explicitly state when to use this tool versus alternatives like list_listen_items or get_listen_stream. There is no exclusion guidance or mention of prerequisites, so an agent must infer the appropriate context from the tool name and sibling list.

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