get-backend-metadata

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

No annotations are provided, so the description carries the full burden. 'Index all backend metadata' implies a read operation, but it doesn't disclose behavioral traits such as whether it's safe (non-destructive), requires authentication (though the schema hints at an optional API key), rate limits, or what 'index' entails (e.g., returns a list, summary, or detailed data). The description adds minimal context beyond the basic action.

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 a single sentence, 'Index all backend metadata', which is front-loaded and efficient. It avoids unnecessary words, but could be slightly more informative without losing conciseness. Every word earns its place, though it's borderline minimal.

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 no annotations, no output schema, and a vague description, the tool's complexity (indexing metadata) isn't adequately explained. The description lacks details on what 'backend metadata' includes, the format of the output, or any constraints, making it incomplete for effective agent use despite the simple parameter schema.

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 input schema has 1 parameter with 100% description coverage, documenting an optional API key for authentication. The description doesn't add any parameter details, which is acceptable since the schema fully covers it. With 0 parameters requiring extra semantics, a baseline of 4 is appropriate as no compensation is needed.

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 'Index all backend metadata' states a verb ('Index') and resource ('backend metadata'), giving a basic purpose. However, it's vague about what 'index' means (e.g., retrieve, list, or catalog) and doesn't distinguish it from siblings like 'list-buckets' or 'get-table-schema', which might overlap in metadata retrieval. It avoids tautology but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'list-buckets' and 'get-table-schema' that might handle specific metadata types, the description doesn't indicate if this tool is comprehensive or for general use, leaving the agent without context for selection.

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