list_profile_alerts

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

No annotations are provided, so the description carries full burden. It only clarifies profileId semantics but does not disclose whether the operation is read-only, destructive, has rate limits, pagination behavior, or what 'all' means (e.g., max results). The list action implies read-only, but not explicitly stated.

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?

Two sentences: first states purpose, second provides critical usage guidance. No redundancy, front-loaded with key information. Every sentence earns its place.

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 no output schema, the description could explain return value structure (what fields alert instances contain). It covers prerequisite calls (get_preferred_profile) but omits default page size, sorting, and whether results are paginated. Adequate but not comprehensive.

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% but descriptions are minimal (e.g., 'Query parameter: page'). The tool description adds value by explaining that profileId selects a configuration profile (lens) and not a container, which helps correct usage. Other parameters (page, read, perPage, archived) have no additional explanation, but the profileId clarification is significant.

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 clearly states the tool retrieves alert instances for a profile, with specific note that profileId refers to a configuration profile (lens, not container). This distinguishes it from sibling tools like get_alert (singular) and update_alert.

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 explicitly instructs to call get_preferred_profile or get_preferences if no profile is specified, and to use preferredProfileId instead of assuming profile 1. This provides clear when-to-use guidance and directs to prerequisite tools.

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