Get All Projects

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

Annotations already indicate readOnlyHint=true. The description adds useful behavioral details: project keys always uppercase, filter configuration, and a possible ValueError. No contradiction with 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?

The description uses a verbose docstring format with extraneous sections (e.g., 'ctx' parameter). The main purpose is front-loaded, but the returns section repeats information from the description and could be more concise.

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?

Given the output schema exists, the description appropriately covers return behavior (uppercase keys, filter) and error handling. Only one parameter with full schema coverage; no missing essential context.

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?

The single parameter 'include_archived' is fully described in the input schema (100% coverage). The tool description adds no further semantics beyond the schema's description and default value.

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?

The description clearly states the verb 'Get', resource 'all Jira projects', and scope 'accessible to the current user', effectively distinguishing it from sibling tools that operate on specific projects or other Jira entities.

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 specifies the context of filtering via JIRA_PROJECTS_FILTER and accessibility, guiding when results are limited. However, it does not explicitly exclude usage for specific project queries or mention alternatives among siblings.

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