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

Annotations only declare readOnlyHint=true, so the description carries real weight here and delivers two non-obvious traits: results come from the vendor-default template page, and paging controls are intentionally withheld pending a verified request contract. That is exactly the kind of caveat an agent needs and would not get from structured fields.

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?

Front-loaded with the action and the return shape, followed by the two caveats, then the endpoint. The 'Sorry: GET /v1/...' tail is a small amount of extra weight but arguably useful provenance; no sentence is filler.

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?

With no output schema, the description correctly enumerates the returned fields, and the vendor-default-page and paging caveats close the main gaps an agent would hit. The only omission is that filtering behavior via the optional params is left entirely to the schema, which is acceptable given full coverage there.

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 description coverage is 100%, with each of the three parameters documented in the schema including the origin hint for page_id. The description adds nothing about the two optional contains-filters, so the baseline 3 applies rather than a higher score.

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?

States a specific verb and resource ('List the page's notice templates') and goes further by defining what a notice template is (reusable subject + opening comment for incidents or maintenance) and enumerating the returned fields. The naming distinguishes it from the sibling sorryapp_list_update_templates, but the description never explicitly says so.

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?

There is no statement of when to use this versus sorryapp_list_update_templates or the various get_* siblings, and the two filter parameters (name_contains, component_name_contains) are never mentioned as a way to narrow results. The only contextual sentence is about paging being withheld, which is behavioral rather than usage guidance.

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