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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the API does not page, all matches are returned truncation-cut at limit, and the underlying endpoint is disclosed. It stops short of describing the truncation metadata format, keeping it at a 4.

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, front-loaded with purpose and returned fields, followed by the non-paging caveat and endpoint. Zero filler and nothing an agent must wade through.

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 carries the burden of describing returns, and it does list the key fields. For a 4-param read-only list tool this is nearly sufficient; only the shape of the truncation/limit metadata is left implicit.

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%, so all four parameters are already documented, which sets a baseline of 3. The description adds value by explaining that limit is a hard cut with no paging ('all matches come back (cut at limit)'), which clarifies a semantic the schema only gestures at with 'the reply says how many were cut'.

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 forms') and disambiguates the domain term by explaining that forms are the checklists and data-entry forms operators fill in. It also names the returned fields (ids, names, enabled flags, created/modified dates), which lets an agent distinguish it from safetychain_get_form without opening either schema.

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 implies browse/list usage versus the sibling get_form by naming the returned collection and the name filter, and 'Filter by name' hints at when to narrow results. However, it never explicitly says when to prefer this over safetychain_get_form or safetychain_search_records, leaving the choice to inference.

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