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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, and the description is consistent with them in all respects, so there is no contradiction. On top of that, the description discloses two non-obvious behavioral features: the tool performs a "live ownership verification" rather than just reading cached state, and it grants only coordination identity. This justifies a score above the baseline 3 for a third read-only tool.

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 definition is two very short sentences with no overhead. The first sentence contains the essential purpose and verification condition, and the second sentence disambiguates the scope of the binding—safe trading and no loss of security. There is no filler, and every word contributes to selection or invocation.

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 an output schema, four fully-documented parameters, and a generous set of annotations (read-only, idempotent, not destructive), the agent is well-equipped. The marginal gap is that the description doesn't describe what happens when live ownership verification fails, which could matter in some invocation paths, but for a read-verification tool this is a minor gap.

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?

All four parameters have detailed descriptions in the schema itself (100% schema-description coverage), including an exact nested transport object with an enum of "local_process", "shared_store" and "streamable_http". The description itself adds no extra information at the parameter level, stop that, so the standard baseline of 3 applies.

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 states the exact action and resource: "Read one Tasq binding after live ownership verification." It uses a specific verb, a specific object, and a clear qualifier, and it separates the read named in the title "current NFH-authenticated Tasq principal-binding" from the creation-oriented sibling prepare_tasq_principal_binding. The added clause "never wallet or effect authority" further reduces ambiguity about what result the binding has.

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?

The description gives a clear context for use: retrieving a binding after "live ownership verification," i.e., the read-only check of an existing binding. It doesn't explicitly name alternatives or say, "when not to use," but the prior is strongly implied by the read-only wording and the existence of the sibling tool. This is clear context without exclusions, so it earns a 4, not a higher 5.

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