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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the operation costs 1 credit per 5 pages, that results are 'Not saved', and that it depends on scan_agent_website output; it stops short of explaining return shape, permissions, or rate limits.

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?

Three short sentences front-load the action, then add the input dependency, credit cost, and persistence caveat. Every sentence carries operational value with no filler.

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 has no output schema and only partial parameter descriptions, so the description should carry more burden. It covers cost, non-persistence, and input origin, but leaves unclear what the returned descriptions/keywords look like or how they correspond to the supplied pages.

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 coverage is 50%: the 'id' parameter is already described in the schema as an Agent UUID from list_agents. The description adds useful meaning for the 'pages' parameter by identifying it as website pages from scan_agent_website, but it does not explain the page object fields (path, title) or mapping 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?

The description states a specific action (writing AI descriptions and keywords) for a specific resource (website pages) and identifies the input source as output from scan_agent_website. It is clear but does not explicitly distinguish itself from nearby sibling tools such as generate_agent_description or save_scan_data.

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 parenthetical '(output of scan_agent_website)' implies this should be used after scanning a website, and 'Not saved' hints at its ephemeral role. However, it does not explicitly say when to use this versus save_scan_data, scan_website_quick, or other description-generation tools.

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