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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real behavioral context: API-token principals are excluded, managed-agent assignment can trigger agent work, repository discovery does not authorize execution, and names may be truncated. These are non-obvious side effects an agent could not infer from 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?

Front-loaded with the purpose, then moves cleanly into behavior, return shape, and pagination mechanics. It is dense and slightly list-like in the enumeration of fields and return pages, but nearly every sentence carries information the agent needs.

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 fully documents the return payload (boards, columns, members, repositories pages, each with items and nextOffset) and the pagination contract. For a 3-param read-only discovery tool, nothing an agent needs to call or page it is missing.

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 0%, so the description must carry the load. It explains offset semantics thoroughly (applies independently per list, follow each list's nextOffset) and the limit range, though the limit bounds are already in the schema. projectId is never described, which is the one remaining gap for a required parameter.

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 ('Discover valid boardId, columnId, assigneeUserId and bound agentRepositoryId values') and scopes it to ticket writes, which cleanly separates it from list_projects, get_ticket, and the write siblings. An agent can tell what it returns without opening the 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?

It sets clear context ('for ticket writes') and names the dependent operations (create_ticket, update_ticket), implying use before those writes. It never explicitly states when NOT to use it or that it is a prerequisite step, so it falls short of a full when/when-not routing statement.

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