link_meta_endpoint_v1_enrich_link_meta_post

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

With no annotations present, the description carries the full burden. It discloses the action (fetching metadata) and the cost (2 credits per request), but does not mention error handling, rate limits, authentication requirements, or the exact structure of the response. Since the tool is a POST endpoint with no output schema, more behavioral details would help the agent anticipate results.

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 exceptionally concise: two sentences, no fluff, and the primary purpose is front-loaded. The cost information is clearly stated. Every sentence earns its place.

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 covers the core purpose and lists expected output items, but without an output schema it leaves ambiguity about the exact response format. It also omits details such as error cases, URL validation, and any rate limiting. For a tool with a single parameter, this is adequate but not comprehensive.

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 parameter is fully described in the schema (100% coverage), so the description adds limited new meaning. It does reinforce that the URL is used to retrieve metadata and hints at the output fields, but this is already implied. The schema already says 'USE THIS TOOL to get page titles and social preview images,' so the description provides no significant extra semantic value beyond what the schema already conveys.

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 states a specific verb and resource: fetches website metadata, listing the key items (title, description, favicon, social preview images). This clearly distinguishes it from the sibling enrichment tools, which target different data types. The tool's name reinforces its purpose.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or contexts where another tool would be more appropriate. The only usage hint appears in the parameter description ('USE THIS TOOL to get page titles and social preview images'), but the main description lacks such direction.

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