Search Medium

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

Annotations already establish read-only and open-world behavior. The description adds a non-obvious pagination contract: nextCursor must be passed back as page for subsequent results. This is useful behavioral context not present in the annotations or schema.

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, front-loaded with purpose and followed by actionable pagination guidance. Every sentence earns its place with no filler.

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?

Invocation-critical details are covered: read-only scope, keyword search, and pagination. Since there is no output schema, the description could say a bit more about what the response contains beyond nextCursor, but for a search tool this is largely sufficient.

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 0%, so the description must compensate. It adds meaning for query (keyword) and page (pagination via nextCursor), but limit is never mentioned. The parameter names and defaults are somewhat self-explanatory, but coverage is only partial.

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 and resource: 'Search all of Medium for posts by keyword.' This clearly distinguishes it from sibling tools like get_feed and get_recent_posts, which are scoped or personalized rather than a global keyword search.

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?

Provides clear context for when to use the tool: when the user wants a global Medium keyword search. It does not explicitly name alternatives or exclusions, but the 'all of Medium' scope makes the intended use distinct from feed/list/reading-list tools.

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