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

The description says it 'Logs the time together immediately,' which is a persistence/write action, yet annotations declare readOnlyHint=true. That is a direct inconsistency between the described behavior and the structured safety hint. The description also does not clarify what gets recorded or whether the log is durable, leaving the conflict unresolved.

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 short sentences, front-loaded with the triggering utterance. Little waste. The example quote adds concrete value rather than padding.

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, and parameters are fully documented in the schema. The main gap is behavioral: the write-like 'logs the time' action is never reconciled with the read-only annotation, leaving an agent uncertain about side effects.

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 description coverage is 100%, so the schema already documents context, contact_id, and contact_name including the either/or requirement. The description adds no parameter-level detail beyond the trigger example. Baseline 3 is appropriate when the schema carries the semantics.

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: it logs time together and returns the whisper briefing for the matched person. The trigger example ('I'm with Sarah') makes the intent concrete. It is fairly distinguishable from siblings, though it does not explicitly name alternatives like proximity.briefing.get.

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?

Gives a clear trigger condition: 'The moment the human says they are with someone.' This tells the agent when to call it. However, it offers no exclusions or explicit comparison to alternatives such as proximity.briefing.get or interactions.log.

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