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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions 'recent post titles' and gives no context about ordering, pagination, failure behavior, or whether the author identifier is required.

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 very short and front-loaded, but it is under-specified rather than efficiently complete. It conveys the core idea without waste, yet omits essential operational details.

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?

The description is incomplete for practical invocation: it does not define the input parameter, provide usage context, or mention any constraints. Even with an output schema available, an agent lacks the information needed to form a correct request.

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 0% and the description does not explain what 'q' means. With only a bare 'q' parameter and no compensation from the description, an agent cannot infer how to specify the author or query.

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 names a specific resource ('Author feed') and the expected output ('recent post titles'), making the tool's purpose reasonably clear. It lacks an explicit verb and does not differentiate it from other content-feed siblings, so it falls short of a 5.

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 about when to use this tool vs. alternatives, no mention of the expected input, and no exclusions. The description simply states what the tool returns without helping an agent decide between Medium and the many other feed/social tools.

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