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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds that the methodology is versioned and that every ranking cites its version, which is useful behavioral context. However, it doesn't disclose return format, size, or any rate limits. With annotations covering safety, this is adequate but not rich.

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 two concise sentences that front-load the resource and its contents. Every word earns its place, and the versioning note is a valuable addition without verbosity.

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?

Given the tool has no parameters, no output schema, and clear annotations, the description provides sufficient context: what the methodology contains and its versioned nature. It doesn't need to explain return values. However, it could mention how to use the version information (e.g., referencing methodology versions in other calls) to be fully complete.

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 there is no parameter semantics to address. The baseline for zero parameters is 4. The description correctly focuses on the resource rather than non-existent parameters.

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 a specific resource ('ranking methodology') and enumerates its contents (weights, tombstone tier definitions, confidence labels, honesty guarantees). It is clear what the tool retrieves. However, it doesn't explicitly differentiate from siblings like get_tombstones or get_ranking, which also deal with ranking-related data.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies this is for understanding ranking mechanics and versioning, but it doesn't state when an agent should call this versus get_ranking or get_tombstones. The usage is implied by the content description.

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