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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds real value beyond that by clarifying that 'selections never authorize changes' and that opening the view mutates nothing, which is non-obvious for a tool that accepts project/task/resource IDs.

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?

Two sentences, front-loaded with the core action and the default-fallback rule. The final clause is slightly redundant with the preceding 'makes no changes' but is short and still informative.

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 read-only view opener with annotations covering the safety profile and no output schema, the description is close to sufficient. The notable gap is the undocumented 'tab' parameter, which an agent could otherwise use to land on the right sub-view.

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 0%, so the description must carry the burden. It meaningfully explains the project/task/library-resource selectors (projectId, taskId, resourceId) and their optionality, but it never mentions the 'tab' parameter or its enum values, and gives no format hints for the UUID fields.

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+resource pair ('Open the project work view in the current conversation'), which is clearly distinct from siblings like open_workspace or open_plugin_settings. It does not explicitly name those siblings as alternatives, so it falls short of a 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?

Explains the fallback behavior ('otherwise use the saved default project when set'), which tells the agent what happens when no selection is made. However, it gives no guidance on when to prefer this tool over the other open_* siblings or what preconditions apply.

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