iaas_get_project_resource_metadata

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing on top of that — no indication of what "resource metadata" actually contains, whether the call can return partial/empty data, or any auth/rate-limit context. It essentially re-states the GET semantics the annotations already encode.

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?

It is short and front-loads the verb+resource, but sentence one and sentence two are near-duplicates, so roughly a third of the text is redundant. The raw REST path is the only sentence carrying new information.

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?

There is no output schema, so the description carries the burden of explaining what a "resource metadata" payload is — and it says nothing about the return shape, whether it is project-level quota/tag metadata, or how it relates to the sibling project-metadata endpoints. For a read tool with an ambiguous resource noun, this is under-specified.

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 the `id` and `apiVersion` parameters are documented in the schema itself. The description's "by a given project id" only echoes the required parameter and gives no extra detail on ID format or version-negotiation behavior, so the schema does all the work — 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?

The description names a verb and resource ("Get project resource metadata") and appends the REST path, which confirms the underlying endpoint. However, the second sentence merely restates the first with "by a given project id," and nothing distinguishes this from the very similar sibling `project_get_projects_by_id_resource_metadata` or from its write counterpart `iaas_update_project_resource_metadata`. Purpose is identifiable but only barely differentiated.

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 statement of when to use this tool, when not to, or which alternative to pick. Given the presence of both `project_get_projects_by_id_resource_metadata` and `iaas_update_project_resource_metadata` in the sibling list, the absence of any routing guidance is a real gap rather than a trivial one.

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