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

Annotations already declare this read-only, idempotent and closed-world, so the description is not burdened with safety disclosure. It adds genuinely non-obvious behavioral context: that 'inputs' reports raw e-ledger field names rather than canonical Open Footprint names, and that published:false means no rules exist and the agent must not fabricate guardrails. It does not sketch the overall response shape, but the anti-hallucination guidance is the highest-value thing it could say.

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?

Three short sentences, each earning its place: the trigger and exclusion come first, then the two caveats about response content. No restatement of the tool name or title, no 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 a single parameter, no output schema, and annotations covering safety, the description covers most of what is needed, including a key anti-fabrication rule. The gap is the undefined 'id' parameter, which leaves ambiguity about whether the lookup is sector-scoped or policy-scoped. Complete on behavior, incomplete on input contract.

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 description coverage is 0% for the single required parameter 'id', so the description must explain it and does not. Nothing states whether 'id' is a sector identifier, a policy identifier, or a standard code, which is the one piece of information an agent needs to form a correct call. The discussion of the 'inputs' response field is helpful but describes output, not the input parameter.

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 purpose: retrieving the validation rules/guardrails that apply to a sector's emissions records. It explicitly separates this from compliance_policies (regulations), so an agent can distinguish it from the nearest sibling. It never identifies the resource by name (policies for a sector), so it stops just short of a fully unambiguous verb+resource statement.

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?

It gives an explicit trigger (user asks which validation rules apply to a sector's emissions records) and an explicit exclusion with a named alternative (do not use for regulations; use compliance_policies). This is exactly the when/when-not/alternative structure that prevents miscalls.

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