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

The description aligns with the annotations (readOnlyHint, idempotentHint, non-destructive) and adds that the tool reads specific contract aspects. However, it provides no additional behavioral details such as side effects, errors, or output behavior beyond what the annotations already imply, so the bar for transparency is only partially met.

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?

The description is a single concise sentence that directly states the action and the subject. There is no extraneous content or unnecessary repetition.

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?

There is no output schema and no clear statement of what the returned contract contains or how it is structured. The phrase 'identity, temporal, dimension, and context-packet contract' hints at fields but does not provide enough context for an agent to know what to expect or how to handle the result.

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 schema has one parameter, 'databank', with no description and 0% schema description coverage. The tool description does not explain what a 'databank' is, what values are valid, or how the parameter affects the result, so the description fails to compensate for the missing schema-level parameter documentation.

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 uses a clear verb ('Read') and names a resource ('a databank's identity, temporal, dimension, and context-packet contract'), but the phrase 'context-packet contract' is jargon-heavy and does not clearly convey what the tool actually returns. It is more specific than a tautology but still vague enough that an agent may not know what this tool does compared to sibling tools like get_entity_evidence or discover_daystruct_capabilities.

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 guidance about when to use this tool versus any sibling tool. The description does not mention alternatives, conditions, or scenarios, so an agent has no basis for selecting this tool over closely related ones.

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