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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what content the tool reveals, but not whether it is a safe read-only operation, what the output looks like, or whether any side effects exist. This is a meaningful gap for an unannotated tool.

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 compact and front-loads the most important question: who made this and who supports it. The philosophical framing adds context but slightly reduces directness. Overall, it is appropriately sized for the tool.

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 no-parameter informational tool, the description conveys the core purpose and content. However, with no output schema, it does not explicitly state what the agent should expect in the response, such as a formatted disclosure statement or structured fields. This leaves some uncertainty but is not fatally incomplete.

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 an empty input schema, so parameter documentation is not needed. The description does not need to explain parameters, and the baseline for a zero-parameter tool is appropriate.

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 the tool's purpose: to reveal who created and funds it, and to disclose conflicts of interest and provenance. It uses a metaphorical but understandable framing. However, it does not explicitly distinguish itself from the sibling tool jhnrd_conflicts, which may also relate to conflicts.

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 this tool is for learning about the tool's own origins and conflicts, but it provides no explicit guidance on when to choose it over siblings like jhnrd_conflicts or jhnrd_status. No alternatives, exclusions, or conditions are given.

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