Site overview

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

The description aligns with the readOnlyHint annotation by stating it explains the read-only scope, which is transparent about its side-effect-free behavior. However, it does not describe other behavioral aspects such as error handling or return format, but the annotation already covers the read-only nature.

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 a single sentence that conveys the two main functions: returning metadata and explaining the read-only scope. It is concise and well-structured without unnecessary details.

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?

The description provides sufficient context for a no-parameter tool by stating its purpose and the fact that it explains the read-only scope. It is complete enough for an agent to understand what the tool does, though it does not specify the exact format of the metadata, which is not critical.

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 no parameters, so the schema coverage is 100%. The description does not add any parameter-specific information because none exist, resulting in the baseline score of 3.

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 that the tool returns public metadata for 'Ventless Fireplace Review' and additionally explains the read-only scope of the server. This is a specific action that distinguishes it from sibling tools that search, list, or get content.

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 does not provide any explicit guidance on when to use this tool versus the sibling tools (search_content, list_content, get_content). It does not mention alternatives or conditions for using this tool, leaving the agent to infer its applicability from the purpose alone.

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