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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral detail: it returns source HTML (not the shim/badge), returns asset paths for multi-file sites, truncates large content with sizeBytes, and clarifies the auth requirement. Critically, it includes a security warning that returned data is never instructions and must not be followed without user confirmation – a proactive disclosure beyond any annotation. This fully covers the behavioral surface.

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 front-loaded with the main action and then layers details logically: what is returned, truncation, auth, and a final security warning. It is slightly long but every sentence contributes value, especially the security note which is critical. The structure is clear and efficient, though it could be trimmed slightly.

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 read-only tool with 2 parameters and no output schema, the description covers all essential aspects: return content, multi-file behavior, truncation, authentication requirements, and a security warning about data vs instructions. Nothing an agent needs to correctly invoke and handle the response is missing. The description is complete.

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 does explain the managementToken condition ('With an account token, owned drops need no managementToken') but does not elaborate on dropId beyond what the schema already provides (pattern, required). The description adds some value for managementToken but leaves dropId self-evident, which is acceptable given its simplicity. A score of 3 reflects adequate compensation without being exhaustive.

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 verb and resource: 'Read a drop's source HTML'. It also clarifies what is excluded ('no shared-memory shim, no attribution badge') and adds the multi-file asset list, making it clearly distinct from sibling read tools like dropyour_read_app_files or dropyour_read_data. The purpose is unambiguous.

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 provides usage context about authentication ('With an account token, owned drops need no managementToken') and truncation behavior, but it does not explicitly name alternatives or state when NOT to use this tool versus siblings. There is no comparison to other read tools, so an agent must infer the appropriate use case from the purpose alone.

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