like_post

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

The description discloses that it 'Creates a like record', indicating a write operation. With no annotations provided, it carries the burden of behavioral transparency, but it omits details like idempotency (e.g., effect of re-liking) or permission requirements beyond authentication.

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 description is only two sentences long, with no redundant information. Every word adds value, making it concise and efficiently structured.

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 simplicity of the tool, the description covers the core action and authentication need. However, with no output schema, it lacks information on the return value (e.g., created record) or error handling, leaving the agent partially informed.

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?

The input schema has 0% description coverage, and the description only mentions 'references the target post' without mapping to the parameters 'uri' and 'cid'. This leaves the agent to guess their meaning, which is insufficient.

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 action: 'Like a post on AT Protocol. Creates a like record that references the target post.' This is specific to liking a single post and distinguishes it from sibling tools like batch_like and unlike_post.

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 mentions 'Requires authentication', which provides a prerequisite. However, it does not explicitly state when to use this tool versus alternatives like batch_like or unlike_post, leaving usage context implied.

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