Retrieve metrics stream

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that it calls a GET endpoint and returns information per workspace, which slightly extends behavioral context but does not disclose significant traits beyond annotations.

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?

The description is two sentences, but the first sentence repeats the title ('Retrieve metrics stream'). It is otherwise concise and front-loaded with the action and result. Slight redundancy reduces efficiency.

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?

No output schema is provided, so the description should clarify return values. It only says 'Returns metrics stream information' without elaboration on structure or contents, and omits error conditions, prerequisites, or pagination details. For a read tool, this is insufficient.

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 100% and the description only paraphrases the schema's ownerId description ('for the specified workspace'). No additional parameter details, defaults, or constraints are provided beyond the schema.

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 clearly states it retrieves metrics stream information for a specified workspace and includes the API endpoint. It distinguishes from siblings like render_get_owner_log_stream by specifying 'metrics stream' vs 'log stream', though it does not explicitly differentiate from other get tools.

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?

The description implies usage for reading metrics stream info but provides no explicit guidance on when to use this vs alternatives like render_upsert_owner_metrics_stream or render_delete_owner_metrics_stream. No when-not or context-dependent advice is given.

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