project_edit_metadata

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the dialog is modal and that the command blocks until the user closes it, an essential scheduling fact. It does not cover save/cancel semantics, but the key blocking trait is disclosed.

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 short sentences with no filler. The purpose is front-loaded, and the second sentence adds the important blocking behavior without redundancy.

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 parameterless dialog-launching tool, the essential operational facts are present: what the dialog is, what it edits, and that invocation blocks until user closure. A note about confirm/cancel outcomes would be nice but is not critical.

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 tool has zero parameters, so the 0-parameter baseline of 4 applies. The description's mention of editable fields is supplementary; there are no schema parameters that need elaboration.

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 provides a specific verb and resource: it opens the metadata editor dialog and lists representative fields. It is clear but does not explicitly differentiate itself from sibling tools, and 'track metadata' is slightly imprecise for a project-level metadata dialog.

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 implied: the tool is for interactively viewing/editing metadata through a dialog. However, there is no explicit when-not-to-use guidance or mention of alternatives such as track_set_properties for programmatic track changes.

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