maasy_get_content_pipeline

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

No annotations are provided, so the description must fully disclose behavior. It mentions filtering by status and time, but does not state whether it is read-only, what authentication is needed, or any other traits. This is insufficient for an agent to understand side effects.

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 short sentence, but it is cryptic and lacks structure. It is not overly verbose, but it fails to efficiently convey key information.

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?

Given the complexity (2 parameters, no output schema, no annotations), the description is incomplete. It does not explain what the tool returns, how the days parameter works (e.g., creation date vs. modified date), or the exact list of statuses. Many details are missing.

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 50% (project_id has description, days does not). The description adds context for 'days' as 'last N days', which clarifies its purpose. However, it does not explain project_id beyond the schema's 'Brand UUID'. Overall, some added value but not substantial.

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 'Content pipeline: drafts, scheduled, published, by status, last N days.' suggests it retrieves content items with various statuses and time range, but lacks a verb and is vague. It distinguishes from siblings like maasy_generate_content but could be clearer. Score 3 is appropriate as it is not a tautology but not fully specific.

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 guidance on when to use this tool versus alternatives, such as maasy_get_alerts or maasy_get_brand_context. The description provides no context for tool selection.

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