get_document_metadata

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

Description claims 'Read-only' but annotations have readOnlyHint=false and destructiveHint=true, indicating it may modify data. This is a direct contradiction, severely reducing transparency.

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 concise sentences with no redundancy, efficiently conveying purpose, usage, and special PDF behavior.

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?

Despite listing returned fields and PDF specifics, the contradiction and missing output schema lead to incomplete context. The read-only claim misleads about behavioral impact.

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 covers 100% of parameter descriptions. The description does not add extra semantic value beyond the schema for the filename parameter.

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?

Clearly states verb 'Get', resource 'document metadata', and specific fields returned. Distinguishes from sibling tools like read_document by noting it gives properties without content.

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 says 'Use this when you need document properties without reading its content', providing clear context. However, it does not name alternative siblings explicitly.

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