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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so this gets credit for going further: it states no authentication is required, that private evidence and hidden prompts are excluded, and that unknown IDs yield an unknown/uncertain result. That is meaningful behavioral context beyond the structured hints, though pagination/size limits are not addressed.

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 sentences, each carrying distinct information: what it returns, where the ID comes from, and behavioral/error caveats. Front-loaded with the core action and free of 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 describing returns and does so (evidence/rule summary, confidence, review/reversal details). Combined with the auth, privacy-exclusion, and unknown-ID notes, an agent has everything needed to call it 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?

Schema coverage is 100% and the single decision_id parameter is fully documented in the schema, so the baseline is 3. The description adds only that the ID originates from get_hourkeeper_history or a public link, a minor supplement over what the schema already states.

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 and resource: reads one public Hourkeeper decision by decision_id. It also names what is returned (evidence/rule summary, confidence, review/reversal details) and distinguishes itself from siblings by pointing to get_hourkeeper_history for the ID and challenge_hourkeeper_decision for review, so an agent can tell it apart without opening other schemas.

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?

Explicitly says where to get the ID (get_hourkeeper_history or a public reference) and routes review requests to challenge_hourkeeper_decision, establishing when to use this tool vs an alternative. It even covers the edge case of unknown IDs, leaving nothing to inference.

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