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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return format (Markdown) and that input may be a bare path, but says nothing about truncation behavior, error cases for unknown pages, or the .md-suffix convention.

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?

Two sentences, front-loaded with the core action and format, followed by the workflow hint. The inline examples earn their space by resolving input-shape ambiguity rather than padding the text.

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?

An output schema exists, so return values and truncation output need no explanation, and annotations cover safety. What remains unexplained—behavior on a missing page or a non-getdroppy URL—is minor for a simple two-parameter read tool.

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 100%, so the baseline is 3. The description goes slightly beyond by showing three accepted url forms, including a "/pricing.md" path, which hints that .md-suffixed paths are valid input in a way the schema's "URL or path" does not. max_characters is left to 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?

States a specific verb and resource ("Read one page of getdroppy.app"), the output format ("as Markdown"), and the accepted input shapes (URL or path). Concrete examples like "/docs/shelf" and "/pricing.md" make the scope unambiguous and distinguish it from search_droppy_docs.

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?

Explicitly positions the tool in a workflow: "Use it after search_droppy_docs to read a result in full." That names the alternative and the sequencing condition. It does not cover non-search entry points or exclusions (e.g., offsite URLs), which keeps it short of a 5.

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