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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly implies a read-only lookup, but does not detail potential side effects, rate limits, or permissions. The simplicity of the operation partially mitigates this, but the description lacks explicit behavioral traits.

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 sentences, highly concise, with the primary purpose front-loaded. Every sentence adds value, and the description is well-structured for quick agent comprehension.

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?

Given the tool's simplicity (one parameter, simple boolean/optional date return), the description is nearly complete. It describes the return shape, though no output schema exists. A slight gap is the lack of behavioral details, but overall it covers the essential context.

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%, fully documenting the 'wallet' parameter with format details (EIP-55 or lowercased, 0x+40 hex). The tool description does not add further parameter context, so a baseline score of 3 is appropriate.

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 clearly states the tool checks for an active 'verified-hireable' subscription on the TensorFeed Agent Directory, specifying the exact boolean and optional ISO date return. The verb 'look up whether' and resource 'wallet subscription status' are specific, distinguishing it from sibling tools like check_agent_reputation.

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 explicitly notes the tool is useful for 'downstream marketplaces or peer agents who want to confirm...before routing work,' providing clear context. It does not explicitly state when not to use or list alternatives, but the sibling tool list implies these exist.

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