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

With no annotations provided, the description must communicate behavioral traits. It indicates the tool performs scoring (likely a read operation) but does not mention whether it modifies anything, requires authentication, has rate limits, or handles invalid URLs. The lack of detail leaves uncertainty for an AI agent.

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 a single, short sentence that front-loads the main action ('Score a website'). It is concise with no wasted words. However, it could be slightly more structured by separating purpose from output dimensions.

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 tool is simple with one parameter and likely a clear output schema (not shown). The description covers the core purpose and dimensions but omits context like prerequisites (e.g., website must be accessible), expected input format, or interpretation of scores. Given low complexity, it is minimally complete but could benefit from a bit more detail.

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 schema has only one parameter (url) with 0% description coverage. The tool description does not explain the URL format, constraints, or what constitutes a valid input. It only mentions the scoring dimensions, which relate to the output, not the parameter. The description adds minimal value beyond the schema for the parameter.

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 tool scores a website 0-100 across specific dimensions (SSL, mobile-readiness, speed, contact, booking). It uses a specific verb 'score' and resource 'website', and the list of dimensions distinguishes it from sibling tools like 'find_no_booking' or 'bulk_audit'.

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?

No explicit guidance is given on when to use this tool versus its siblings (e.g., bulk_audit for multiple sites, find_no_booking for a specific issue). The description implies it's for a single website audit but does not state this explicitly or provide exclusions.

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