list_metadata_schema

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds only the endpoint and 'Read Metadata', which does not provide additional behavioral context such as what the response contains or any authentication requirements. It does not contradict annotations but offers minimal value beyond them.

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 very concise (two short lines) and front-loaded with the verb and endpoint. However, it is so minimal that it fails to convey necessary meaning; conciseness should not sacrifice clarity. It is appropriately sized but under-informative.

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?

Even though an output schema exists (which covers return values), the description does not clarify what 'Metadata' refers to or that this tool returns the schema for metadata definitions. The lack of differentiation from list_metadata and the absence of any explanatory context make it incomplete for an agent to correctly invoke it.

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 tool has zero parameters, and schema coverage is 100% (trivially satisfied). With no parameters to document, the baseline of 4 applies. The description does not need to explain parameters, and it doesn't.

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 states 'Read Metadata' which is too generic and doesn't specify that this tool returns the schema definition for metadata. It does not distinguish itself from sibling list_metadata, which likely retrieves actual metadata entries. The endpoint is provided but the purpose remains ambiguous without context.

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 use this tool versus alternatives like list_metadata or other *_schema tools. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent without direction.

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