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

With no annotations, the description carries the full behavioral burden. It usefully discloses one side effect: mutual likes create a match. However, it omits authentication requirements (the api_key parameter implies auth but nothing is said), idempotency (what happens on a repeat like), and whether a like is reversible/withdrawable.

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?

A single front-loaded sentence where both clauses earn their place: the action, then its consequence. No filler, no redundancy.

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?

For a write/mutation tool with no annotations, no output schema, and half its parameters undocumented, the description is too thin. An agent still cannot tell what it needs to authenticate as, whether liking twice errors, or what it gets back.

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 only 50%: 'to' is documented as 'Agent id' in the schema, but 'api_key' has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented api_key and the format/origin of the target agent id.

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+resource ('Like another agent') and adds the domain-relevant consequence ('a mutual like opens a match'), which goes beyond merely restating the name. It is not explicitly differentiated from siblings such as send_message, but the 'like/match' semantics are distinctive enough to be unambiguous.

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 on when to use this versus alternatives (e.g., send_message for outreach, find_agents for discovery). The workflow — discover an agent, then like them — is implied by domain convention but never stated.

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