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

With no annotations provided, the description must fully disclose behavior. It only mentions parsing sitemap.xml URLs but doesn't specify return format, error handling, support for sitemap indexes, or any other behavioral details. This is a minimal disclosure for a tool with no annotation coverage.

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, direct sentence with no extraneous information. Every word is meaningful, making it highly concise and well-structured.

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, so a short description is somewhat justified. However, without an output schema or annotations, the description should explicitly indicate what the tool returns (e.g., a list of URLs) and any notable edge cases like sitemap index files. It covers the basic function but leaves these details implied.

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 input schema lists a single 'url' string with no description, and schema coverage is 0%. The description helps by clarifying that the URL should point to a sitemap.xml file, adding meaning beyond the bare schema. However, it doesn't provide details about URL formats or constraints, so the compensation 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?

The description clearly states a specific action ('Parse') and a specific resource ('sitemap.xml URLs'), making the tool's purpose understandable. It doesn't explicitly differentiate from sibling tools like xml_parse or crawl, but the focus on sitemaps is distinctive enough.

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 guidance is provided on when to use this tool versus alternatives such as crawl, map_site, or feed_parse. The description only defines what the tool does, leaving the agent to infer usage context.

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