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

The description clearly states that the tool writes a business fact sheet and stores it as site content, which matches the mutating behavior implied by readOnlyHint=false. It also adds useful context about server-side crawling and the SPA limitation that can cause little text, going beyond the annotations without contradicting them.

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 compact and front-loaded: the main action, scope, and outcome appear in the first sentence, with a relevant caveat in the second. Every clause earns its place and nothing is redundant.

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?

For a side-effecting, multi-step tool with no output schema, the description covers the main behavior and the key SPA caveat but omits what the agent can expect in return, whether existing site content is overwritten, and how failures are reported. It is adequate for a simple call but incomplete for confident operation.

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 description coverage is 0%, so the description must compensate. It mentions 'up to 30', which loosely relates to the max_pages bound, but it never names or explains the url parameter or how max_pages controls behavior. The agent gets no guidance beyond the schema's raw constraints.

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 uses a specific verb ('crawls') with a clear resource ('a published website') and explains the outcome: writes a business fact sheet and stores it as agent site content. It is clear on its own, but it does not distinguish itself from the sibling tool oryksa_learn_site, which may overlap in 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?

There is no guidance on when to use this tool versus alternatives such as oryksa_learn_site, oryksa_links, or oryksa_set_allowed_domains. The SPA caveat is a limitation, not a usage condition, and no exclusion or preferred-context criteria are provided.

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