jira_search_assignable

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

Annotations declare readOnlyHint=true, so safety is covered. The description adds the assignability constraint (permission-aware result set), which is meaningful behavior beyond the schema. But it doesn't state result limits, pagination, or that it's scoped to a single issue's assignability.

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?

Single sentence, front-loaded with the verb and the key constraint (assignable). No waste.

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 2-param read-only search, the description plus schema is minimally sufficient to call correctly. But it lacks differentiation from sibling user-search tools and the freshness/completeness of the assignable list, which matters for agent routing.

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% – both key and query are documented with format and match semantics. The description adds nothing beyond 'assignable to an issue', so baseline 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 (Search) and resource (users assignable to an issue). This distinguishes it from jira_search_users (searches all users) and find_jira_user, though it doesn't explicitly call out the differentiation.

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?

Implies usage via 'assignable to an issue' – you'd use it when finding someone to assign a specific issue. But no explicit when-to-use vs jira_search_users or find_jira_user, and no guidance on permissions or filtering.

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