get_metadata_with_tokens

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

No annotations provided, so description carries full burden. It details token decoration, empty tokens, untokenized attribute, layout omission, composition stripping, and format options. Lacks explicit idempotency statement but is otherwise transparent.

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?

Single dense paragraph with key info front-loaded. Efficient but could be broken into bullet points for readability.

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 11 parameters and no output schema, description is fairly complete on behavior but misses parameter details. Adequate for a read operation but could be more thorough.

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%. Description explains layout, format, includeComposition, but leaves url, nodeId, fileKey, onlyGaps, withVectors, onlyWithTokens, withComponents undocumented – 7 of 11 parameters not described.

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 it returns an XML tree with tokens, identifies itself as step 2 of a recommended flow, and distinguishes from list_tokens.

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 'STEP 2 of the recommended flow (call list_tokens first...)' and explains when to use various parameters like layout, format, includeComposition.

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