get_entities_by_ids_with_projection

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

With no annotations provided, the description bears full burden of behavioral disclosure. It only states 'retrieve' (read operation) but omits essential traits like pagination (implied by 'max_page_size' parameter but not explained), error handling for invalid IDs, or rate limits. This is insufficient for an agent to invoke safely.

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 extraneous information. The purpose is front-loaded, and every word adds value. Excellent structure for quick agent consumption.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It omits crucial context like pagination behavior, response format, error scenarios, and prerequisites (e.g., valid IDs). An agent would lack sufficient information to use this tool correctly.

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%, requiring the description to compensate. It adds minimal value: 'specific fields' hints at 'projection', 'IDs' at 'entity_ids', 'batch' at multiple IDs. But it fails to explain 'collection' or 'max_page_size', leaving their meaning and usage unclear.

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 specific fields from multiple NMDC entities by IDs, with batch and filtering capabilities. It effectively distinguishes from sibling tools like 'get_entity_by_id' and 'get_entity_by_id_with_projection' by emphasizing batch operations and field filtering.

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?

Description explicitly says 'Use this tool for batch operations' and 'retrieve specific fields', providing clear context for when to use. However, it lacks explicit exclusionary guidance or mention of alternatives, which would help disambiguate from similar sibling tools.

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