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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the concrete output formats (Markdown vs stripped text) and the 40,000-character cap, which are behavioral details not covered by annotations. This adds value beyond the structured data.

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 one sentence, front-loaded with the action and resource, and every element earns its place: the URL scope, the output format, and the character limit. Extremely efficient and clear.

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?

Given the tool is a simple read operation with a single parameter repeated in the schema, the description is sufficiently complete. It doesn't explain what 'stripped text' means or how to specify the format (since there's no format parameter, it implies the agent can select, but that might be a minor gap). Output schema is absent, so the description doesn't need to cover return values. The tool is simple enough that missing details are unlikely to cause incorrect invocation.

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 one parameter 'url' with type 'uri' and no description, so schema coverage is 0%. The description does not elaborate on the url parameter, but the parameter format is obvious from the schema (a URI). Since there is only one parameter and its purpose is evident from the tool's name and the description's mention of the site, a baseline of 3 is appropriate; the description does not significantly add meaning beyond the schema.

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's action ('Read'), the specific resource (https://gcwars.com page), and the output formats (Markdown or stripped text). It also includes a useful limit (40,000 characters). This distinguishes it from siblings like search_pages and site_info, which perform different operations.

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 implies usage: when you need to read a page from that site. It does not explicitly compare to siblings, but the tool name and description make it clear. There's no 'when not to use' guidance, but it's not misleading. It could mention that search_pages is for finding pages, but this is implicit.

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