maasy_get_content_pipeline

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

With no annotations, the description carries the transparency burden, and it does disclose key filtering behavior (statuses and time window). However, it does not state read-only nature, return format, or how project_id scoping behaves, so transparency is partial.

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 compact fragment with no filler and front-loads the resource name. It is concise but omits a verb and contextual qualifiers, so it falls just short of maximally effective.

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?

Without output schema or annotations, the agent needs more context about what the tool returns and how the parameters interplay, but the description only gives a terse state list. The tool is simple, yet the description still feels under-specified for selection and 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?

The schema covers project_id with 'Brand UUID,' and the description's 'last N days' adds meaning to the days parameter, which is otherwise only a number with a default. Still, descriptive links between parameters and behavior are minimal, leaving some interpretation to the agent.

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 identifies the resource as 'content pipeline' and specifies its scope with 'drafts, scheduled, published, by status, last N days,' which distinguishes it from sibling get_* tools. It lacks an explicit verb, so it reads as a noun phrase rather than a directive, but the intent to retrieve pipeline content is clear.

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?

No usage context is provided; the description does not state when to choose this tool over alternatives like maasy_get_daily_summary or maasy_get_campaign_metrics. No exclusions or prerequisites are mentioned.

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