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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely new context beyond that: results are restricted to authorized resources, and items carry opaque IDs and native revisions, which signals no cross-tenant leakage and a revision-tracking identifier. It omits pagination behavior and result ordering, which matter for a browse operation.

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 compact sentence with the verb and permission scoping front-loaded. The trailing clause about opaque IDs and native revisions is somewhat jargon-dense but carries real information, so little 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?

An output schema exists, so return values needn't be described. Still missing for a paginated, enum-driven browse tool: what the kind values mean at a high level and how to page with limit/cursor. The description is serviceable but leaves an agent to infer both.

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 coverage is only 33% (only cursor is documented), and the description partially compensates by explaining that kind selects one studio domain — useful framing for an 11-value enum. It says nothing about limit semantics (page size, max 50) or the cursor's pagination loop, so the coverage gap is only partly filled.

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 verb "Browse" and the object "authorized studio resources" convey a listing operation, and "optional kind selects one studio domain" implies the resource type is parameterized. However, the description never says "projects" as the tool name does, and it does not distinguish this listing from siblings such as list_assets, list_studio_documents, or native.list_genads_projects.

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?

There is no guidance on when to choose this over get_project (single item), native.list_genads_projects, or other list tools. The phrase "optional kind selects one studio domain" hints at filtering behavior but never states when to supply kind versus omit it.

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