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

No annotations provided, so description must bear disclosure burden. It notes 'Always free, for any caller' suggesting no restrictions, but does not explicitly confirm read-only, side effects, auth needs, or rate limits. Adds 'curated' but lacks complete behavioral context.

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 with front-loaded content types and filter guidance. No wasted words.

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 no output schema, description should clarify return format (list vs. single) and pagination. It implies multiple items ('repos, catalogs, roadmaps') but not explicit. Lacks details on ordering, limits, or error handling.

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 has 100% parameter description coverage; description adds 'Filter by topic, role, and/or category' which mirrors schema info without additional semantics like combination behavior.

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?

Description clearly states tool returns 'Landed's free learning content' including specific types (interview-prep repos, portfolio-project catalogs, role roadmaps) from the landedjobs GitHub org, distinguishing it from sibling tools for job forms and job 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?

Explicitly states filtering by topic, role, and/or category, and implies use for learning content versus job-related siblings. No explicit when-not-to-use or alternatives beyond context.

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