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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the set of returned fields, with no note on result caps, ordering, or total counts — modest added value on top of the annotations.

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?

Three short sentences with the resource and returned fields front-loaded; nothing is padded. The trailing endpoint path is mildly redundant technical detail but costs little.

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 two-parameter read-only list tool with a fully described schema and rich annotations, the description covers what the tool returns and how to chain it with other tools. Pagination behavior is delegated to the schema, which is acceptable, and no output schema exists so field disclosure here does real work.

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%; both page_no and page_size are fully documented in the schema, including the 1-250 range and the instruction to pass next_page_no from the previous reply. The description adds nothing beyond that, 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?

States a specific verb (list) and resource (forms/screens in the organization) and names the fields returned (id, name, version, status). It also names the follow-on tools (get_form, search_entries), which implies the list-vs-detail split, though it never explicitly contrasts itself with a sibling listing tool because none exists.

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?

Usage is only implied: the agent infers it should call this to discover forms before calling formsonfire_get_form or formsonfire_search_entries. There is no explicit when-to-use or when-not-to-use statement, and the endpoint hint 'GET /screen/form/search' is implementation detail rather than selection guidance.

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