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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description adds little behavioral detail. It does signal that the response is a policy document rather than a live operation, but doesn't describe freshness, scope, or format of the returned policy.

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?

One sentence, front-loaded with the verb and the three policy areas. No filler and no redundancy relative to the title.

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-argument, read-only, idempotent retrieval tool with full annotation coverage and no output schema, the description covers the essential scope. It could be stronger by naming the difference from siblings or hinting at the returned structure, but it is sufficient to call correctly.

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?

Zero parameters, so per the rubric baseline is 4. The description correctly implies the tool takes no arguments by enumerating what is returned rather than what must be supplied.

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 uses a specific verb ('Return') and names three concrete policy domains owned by GhostKey, so an agent knows exactly what it yields. It doesn't explicitly distinguish itself from the sibling tools, but the policy retrieval framing is clearly different from catalog/quote/status by resource.

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 when-to-use guidance, no mention of how it relates to ghostkey_catalog, ghostkey_quote, or ghostkey_status. The agent must infer that this tool is for policy questions rather than pricing or inventory. Nothing states when this tool should not be used.

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