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

Annotations already establish the safe read-only/idempotent profile, and the description goes well beyond by disclosing the return shape: each row's value, enforcement mechanism, source, and status taxonomy (including 'closed' rules kept by number) plus an explicit 'under_review' list. This is unusually rich behavioral context for a read 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?

Dense but organized: the core purpose is front-loaded, then return contents, then parameter notes. The enumeration is long, but each clause conveys distinct information rather than filler.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, covering row structure, statuses, and the under_review list. Nothing needed to invoke or interpret the result is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value: it clarifies that product has only one valid value today and gives concrete topic examples. It slightly exceeds the schema's own wording, though it doesn't add new filtering semantics.

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 ('Get') and resource ('the Mandate Vault rulebook') and then enumerates the exact rule categories returned. No sibling tool overlaps with rulebook retrieval, so the agent can immediately tell what this does.

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?

Gives clear context on the topic filter ('pass topic to filter to one section, e.g. Fees or Supply auction') and notes product is always 'mandate-vault' today. There are no real alternative rulebook tools to exclude, so explicit when-not guidance is unnecessary.

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