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

Annotations already declare readOnlyHint/destructiveHint=false, so 'Read-only' is redundant, but the description adds genuinely new information: results are paginated and each item carries status, step/connection counts, and any bound sprint/epic. With no output schema, that field inventory is the main behavioral disclosure. Pagination boundaries themselves live in the schema, not the prose.

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?

A single dense sentence with the resource and module front-loaded, followed by the returned fields and a safety clause. Nothing is wasted and nothing important is buried.

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 3-parameter read tool with annotations and no output schema, the definition covers scope, result shape, and safety. The only real gap is how it relates to get_process / list_process_insights, which an agent might need when choosing a tool.

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 only 33% — projectId is documented, page and limit have type/default/min/max but no prose. The description's 'paginated' and 'in a project' hint at the two undocumented parameters' roles but give no guidance on limit choice or paging behavior, so it only partially compensates.

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 ('Paginated list of process models') and scopes it to a project and the Optimize module, which separates it from the many other stride list_* tools. It also enumerates the returned fields (name, status, step/connection counts, bound sprint/epic). It stops short of explicitly contrasting with get_process or list_process_insights, so 4 rather than 5.

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: 'in a project' plus 'Read-only' tells the agent this is the enumeration entry point, but there is no explicit when-to-use, no mention of get_process for full detail, and no pointer to list_process_insights as the alternative for analytics. An agent must infer the routing itself.

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