bitemporal_truth_status

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

No annotations are provided, so the description carries the full behavioral burden, and it says almost nothing. 'Summarize' weakly implies a read, but there is no disclosure of permissions, side effects, mutation risk, caching/freshness semantics, or what a 'support state' means. For a bitemporal status tool with zero annotation coverage, this is a substantial gap.

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?

A single front-loaded sentence with no filler; the issue is under-specification rather than verbosity. It is as short as it can be while still naming an operation.

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?

An output schema exists, so return values need not be explained, but that is the only structural aid. With no annotations, no parameter documentation, and undefined terminology, an agent lacks enough context to call this confidently or to prefer it over the sibling truth tools.

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 0% and work_ref has no description in the schema. The description's 'one WorkIdentity' hints that the parameter is a scoping identifier, but it never states what form work_ref takes or how it relates to a WorkIdentity, so it only partially compensates for the coverage gap.

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?

It names a verb ('Summarize') and a scope ('one WorkIdentity'), so the operation is identifiable, but the core resource phrase 'current BTTM/1 support states' is opaque jargon that an agent cannot decode without domain knowledge. It also offers nothing to distinguish it from the many truth-related siblings like truth_at, truth_assertion_status, or record_truth_assertion.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as truth_at or truth_assertion_status, which sit in the same truth-assertion family. The agent is left to infer the selection criterion entirely.

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