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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: no indication that this is a read-only operation, no pagination behavior, no statement of what happens when the workspace has many edits. Worse, 'all edits' mildly conflicts with the schema's limit parameter defaulting to 20, so the description overstates the completeness of the result.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though the word 'all' is the one term that should have been qualified rather than kept.

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 two-parameter list tool with no output schema and no annotations, this is minimal but barely viable. The agent still lacks the return shape and pagination behavior, and the 'all' versus limit=20 tension is unresolved.

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 100%, so both parameters are already documented (workspaceId and limit), and the baseline is 3. The phrase 'in a workspace' reinforces the required workspaceId but adds no syntax or semantics beyond the schema, and it never mentions the limit control.

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 ('List all edits') and usefully disambiguates the term by equating edits with projects. It does not, however, distinguish itself from siblings like get_edit, get_edit_full, or list_workspaces, so the agent must infer the boundary.

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?

No guidance on when to use this listing versus get_edit, get_edit_full, search_workspace, or review_edit. The only implicit context is the workspace scoping, and there is no statement of prerequisites or exclusions.

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