site_info

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

With no annotations provided, the description carries the full burden. The word 'Read' signals a non-mutating, safe operation, which is the key behavioral trait for this tool, and the enumerated return fields confirm it is informational. It says nothing about auth requirements, permissions, or whether the data is cached, but for a zero-parameter read of static site metadata the disclosed risk profile is adequate.

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?

A single short sentence with the verb and returned fields front-loaded and no filler. Every word earns its place.

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 exists, so the description wisely lists the fields returned (title, url, version), which is exactly what an agent needs before calling it. Since there are no parameters or annotations, little else is required; only usage timing remains uncovered.

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?

There are zero parameters and the schema is empty, so there is nothing for the description to disambiguate. The baseline for a parameterless tool 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?

States a specific verb and resource ('Read basic site information') and even enumerates the returned fields (title, url, version), so the agent knows exactly what this yields. It does not explicitly contrast with any sibling, though none of the siblings (tags/images/posts/pages CRUD) overlap with site metadata, so confusion risk is low.

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 offers no when-to-use or when-not-to-use guidance and names no alternatives. Usage can only be inferred from the name and verb, which is thin for a tool meant to be selected among 16 siblings.

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