maasy_get_alerts

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only, if it requires specific permissions, or any side effects. The name implies a read operation, but no explicit behavioral details are given.

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 that immediately states the topic ('Pending copilot alerts') followed by a list of categories. It is brief, but lacks a verb for the action. However, it is front-loaded and not verbose.

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 that there are 20 sibling tools and no output schema, the description is incomplete. It does not explain what a 'pending copilot alert' is, how the response is structured, or how results are ordered. An agent cannot fully understand the tool's output without additional information.

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 description does not mention either parameter. The schema provides a description for 'project_id' but not for 'limit'. With 50% schema description coverage, the tool description fails to compensate by explaining how parameters affect results or their meaning in context of alerts.

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 lists alert categories ('campaign anomalies, lead opportunities, content gaps, SEO drops') but uses no verb like 'get' or 'retrieve'. It indicates the tool returns pending copilot alerts but does not clearly state the action, and it fails to differentiate from siblings like 'maasy_get_campaign_metrics' or 'maasy_get_seo_status' which might return overlapping data.

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 is provided on when to use this tool versus its siblings. There is no mention of prerequisites, context for when alerts are available, or cases where the tool should be avoided.

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