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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes further by disclosing the exact fields returned and the underlying API endpoint. With no output schema present, listing the returned fields is genuinely additive context rather than repetition.

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 and tight: one sentence covering scope, fields, and the default/archived switch, plus a short endpoint note. The trailing 'Breeze: GET /api/forms/list_forms.' is implementation trivia that adds little for an agent deciding how to call the tool.

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 one-parameter, no-output-schema list tool, the description covers scope, defaults, and return fields, which is close to complete. The only missing piece is disambiguation from the closely named form-entry and form-field siblings.

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% and the single parameter's own description already states 'true = list archived forms instead of active ones.' The description restates that default/override behavior but adds no syntax or interpretation beyond the schema, so the baseline of 3 applies.

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?

Specific verb+resource ('List the church's online forms') with the returned fields named (id, name, url_slug, is_archived), so an agent knows exactly what it gets. It does not, however, distinguish itself from related siblings like breeze_list_form_entries or breeze_list_form_fields, which an agent could easily confuse for this one.

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 active-vs-archived default is stated, which implies when each mode applies, but there is no explicit guidance about when to reach for this tool versus breeze_list_form_entries or breeze_list_form_fields. Usage is inferable from the description but not spelled out.

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