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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds one genuinely new behavioral fact — results are returned newest first — but says nothing about scoping ('your' is implied to be tenant-scoped) or the two response shapes the schema hints at.

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, front-loaded sentence with no filler. It is arguably too terse for the raw 'studio_project rows' phrasing, but nothing in it is wasted.

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 low-complexity, zero-required-parameter read tool with full schema coverage and no output schema, the description plus annotations give enough to call it correctly. Only minor gaps remain (tenant scoping, item fields), and those are outside its practical burden.

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% and both parameters (limit, cursor) are documented in detail, including the legacy bare-array vs { items, next_cursor, limit } behavior. The description adds no parameter meaning beyond the schema, so the 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 ('List') and resource ('studio_project rows') plus a default ordering ('newest first'), so an agent knows this is an enumeration of studio projects. It does not differentiate from the sibling studio_project_read, nor clarify why 'rows' rather than projects, leaving a small ambiguity for a reader unfamiliar with the data model.

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 only implied: the description tells you it lists all of your projects, so an agent can infer this is the discovery entry point before studio_project_read/update/delete. There is no explicit 'use this when' statement or exclusion against alternatives.

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