list_status_page_severities

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral context beyond noting it returns a list. No mention of pagination, rate limits, or 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?

Concise with a single-line purpose and args/returns breakdown. No unnecessary text, though the structure is purely functional.

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?

For a simple list tool with annotations and an output schema, the description covers the essential action and parameters. It could note potential errors, but completeness is adequate for standard usage.

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?

Description explains status_page_id as 'The ID of the Status Page' and query_model as 'Optional filtering parameters'. Schema coverage is 0% for top-level parameters, but subfields have descriptions. The description adds basic meaning but does not fully compensate for the lack of schema descriptions.

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?

Clear verb 'List' and specific resource 'Severities for a Status Page' by ID. Distinguishes from sibling tools like list_status_page_statuses and list_status_pages, as it targets a different sub-resource.

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?

States when to use (list severities for a given status page) but lacks explicit guidance on when not to use or alternatives. No comparison to similar list functions, though the name and description imply the correct context.

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