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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral nuance that while 'activation' is off (default) business proceeds either way, which is real added context. However, it says nothing about what is recorded on failure, whether the url must be reachable, or any rate/permission constraints.

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 short sentences, front-loaded with the 'Bot meets bot' framing and the actual question to ask. Little waste, though 'Trust Switch' is used before being defined and the negation ('Not a recommend gate') sits at the end.

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 five undocumented parameters, no annotations, and no output schema, the description should do substantially more. It covers intent and the activation flag but never explains the url identity, who 'asker' is, what 'context' should contain, or what gets returned from a recorded handshake.

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 none of the five parameters are described in the schema. The description only obliquely explains 'activation' (default off, does not gate) and 'their_answer' (records yes/no); url, asker, and context are left entirely undefined. For a 5-param tool with zero schema documentation, this is a significant 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?

The description gives a concrete action ('ask "Are you on Trust Switch?"' and 'Records yes/no') against a specific resource (another agent or vendor), which is more than a restatement of the name. It also explicitly differentiates from the sibling trust_check. The undefined jargon 'Trust Switch' keeps it from a 5, but an agent can tell what the tool does.

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?

Timing is stated precisely ('before dealing with another agent or vendor') and an explicit exclusion plus alternative is given ('Not a recommend gate; use trust_check for that'). It does not cover prerequisites or what to do when the counterparty answers no, but the when/when-not framing is clear.

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