get_metadata

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

No annotations are provided, so the description must fully disclose behavior. It only covers filtering logic and does not mention safety (read-only nature), performance implications, pagination, or authentication needs. For a read tool, it should explicitly state it is non-destructive.

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 extremely concise with three sentences. The first sentence states the core purpose, and the next two clarify filtering strategies. No unnecessary words or repetition.

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?

The tool has two optional parameters, no required ones, and an output schema exists. The description covers three filtering scenarios (none, by key, by doc_id) but fails to specify the behavior when both filters are applied (e.g., conjunction or disjunction). It also omits potential ordering or limit information. The output schema may compensate for return value clarity, but behavioral context is incomplete.

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 schema has 0% description coverage (no descriptions in the schema). The description compensates fully by explaining the meaning of each parameter: 'Filter by key to find all values for a key' and 'Filter by doc_id to find all metadata for a document.' It adds significant semantic value beyond 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?

The description clearly states the tool retrieves metadata entries with optional filtering by key or doc_id. The verb 'retrieve' and resource 'metadata entries' are specific. It distinguishes itself from siblings like set_metadata (which writes) and implies a read-only operation.

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 explicit guidance on when to use each filter: 'Omit both to get all metadata,' 'Filter by key to find all values for a key,' 'Filter by doc_id to find all metadata for a document.' However, it does not discuss when to avoid using this tool or mention alternatives like search.

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