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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond the annotations by disclosing that each entry carries a legal source and a 'verify: true' flag indicating unverified values, which tells the agent the data is not uniformly trustworthy.

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 action and scope, with the return-relevant detail (legal source, verification flag) appended efficiently. No wasted words.

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?

No output schema exists, so the description must carry the return-value burden, and it does partially by naming legal source and the verify flag. What remains underspecified is the scope of 'every rule' relative to the tp_thresholds sibling and the overall output shape.

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 takes zero parameters, so the baseline of 4 applies. With no arguments to misinterpret, there is nothing further the description needs to add here.

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 gives a specific verb+resource (list every rate and threshold groTAX uses) and disambiguates the vague tool name 'get_rules' into a concrete catalog of rates/thresholds with legal sources. It does not, however, differentiate itself from the sibling grotax_tp_thresholds, which also concerns thresholds.

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?

Usage is implied: call this to enumerate the full rate/threshold catalog when you need legal sourcing or verification status. There is no explicit when-to-use, when-not-to-use, or pointer to the overlapping tp_thresholds sibling, leaving the agent to infer the boundary.

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