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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, so the safety profile is covered. The description adds that discovery grants no execution authority and points to call_studio_tool for invocation, but gives no details on auth, rate limits, or response behavior.

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?

Three tight sentences, front-loaded with the purpose. The invocation and authority notes are useful, though 'compatibility tools retain their public names' is cryptic and may not earn its place without more context.

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 tool with annotations covering safety and an output schema, the description covers purpose and the discovery/execution boundary. However, with 0% parameter schema coverage, it should explain the three inputs, especially limit and cursor for pagination.

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 explain toolset_id, limit, and cursor. It only alludes to a toolset implicitly and never explains pagination or the identifier's role, leaving all three parameters essentially undocumented.

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 gives a specific verb ('Read') and resource ('canonical native tool schemas and skill references') for a toolset, and distinguishes discovery from execution via call_studio_tool. However, jargon like 'nested toolset' and 'compatibility tools' slightly blurs the exact scope compared with siblings such as list_toolsets.

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?

It clearly frames the tool as discovery-only and states that discovery grants no execution authority, implying that execution should go through call_studio_tool. It does not, however, mention alternatives like list_toolsets or read_skill, nor does it describe when not to use this tool.

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