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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds useful context by labeling the data as 'public' and 'machine-readable', which informs the agent about accessibility and response style. It does not contradict the 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 a single, focused sentence with no filler. It places the core purpose upfront and names both the identity and discovery aspects without redundancy.

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?

For a zero-parameter, read-only discovery tool, the description is nearly complete: it tells the agent what to expect (site identity and machine-readable endpoints) and the annotations cover side-effect safety. Because there is no output schema, slightly more detail about the exact shape of the returned identity/discovery data could have elevated this further, but it is adequate for invocation decisions.

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, so the schema already fully documents the input contract and the description does not need to explain parameter meaning. The baseline of 4 for no-parameter tools applies, and there is no missing parameter information to compensate for.

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 specific verb ('Return') and resource ('public site identity and machine-readable discovery endpoints'), making it immediately clear what the tool provides. It also distinguishes itself from sibling content tools like get_content and search_content by focusing on site-level metadata rather than content retrieval.

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 discovering site identity and endpoints, but it does not explicitly state when to prefer this tool over siblings or when not to use it. An agent can infer the right context from the noun phrases, but there is no direct routing guidance.

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