voicestudio_read_resource

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one behavioral constraint (rejection of unadvertised namespaces), but says nothing about the returned content shape or error format.

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 sentences, front-loaded with the core action and followed by the key constraint. No filler, no restatement of the tool name.

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?

With no output schema, the description would ideally hint at what a resource read returns, but it omits the return shape entirely. The namespace-acceptance rule covers the main failure mode, and annotations cover safety, leaving the definition adequate but not complete.

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 single uri parameter has 0% schema description coverage, so the description carries the burden and does so with concrete format examples (voice://<profile_id>, history://recent). It stops short of enumerating the full set of accepted namespaces, so an agent still has to guess at edge-case URIs.

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 (native MCP resource), plus concrete URI examples (voice://<profile_id>, history://recent) that make the target unambiguous. It distinguishes the tool implicitly from API/job-oriented siblings like voicestudio_call_api or voicestudio_start_job, but never names an alternative to route against explicitly.

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 by the URI-based examples and the constraint that only the backend's advertised namespaces are accepted, which steers the agent toward valid inputs. However, it never states when to prefer this over voicestudio_call_api or voicestudio_call_native, nor any prerequisite for discovering valid namespaces.

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