get_bias_map

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

No annotations, so description carries the burden. It describes output (bias report) but does not disclose side effects, permissions, or data freshness. The behavior is inferred as a read-only analysis, which is reasonable but not explicit.

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?

Two tight sentences with no superfluous words. The first sentence states the main function, the second adds context and usage. Efficient and well-structured.

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 one optional parameter and no output schema, the description covers the tool's purpose, output, and usage context adequately. It specifies the scope ('resolved assessments') and gives a concrete use case.

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?

Parameter 'domain' described similarly in schema and description ('Filter to one domain. Omit for full cross-domain map.'). Description adds no extra meaning beyond schema, but schema coverage is 100%, so baseline of 3 is appropriate.

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?

Clearly states the tool generates a structured bias report across resolved assessments, distinguishing it from siblings by focusing on bias detection and calibration. The verb 'Generate' and resource 'bias report' provide specific purpose.

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 'Use for quarterly self-calibration review,' giving clear context for when to use. Does not mention when not to use or alternatives, but the intended usage is well-defined.

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