Sample Details Lookup

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Get' implying a read-only operation, but does not disclose any behavioral traits such as authentication requirements, rate limits, error handling for invalid IDs, or output characteristics beyond the existence of an output schema. This is insufficient for a tool with zero annotation coverage.

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 that is concise and front-loaded with the key action and resource. No filler or redundant information.

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 the low complexity (one required parameter, output schema exists), the description covers the basic purpose and usage. However, it lacks details on error scenarios (e.g., invalid ID), what 'comprehensive metadata' includes, and any behavioral context (like rate limits or authentication), making it minimally complete but with gaps.

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 one parameter 'entity_id' with 0% schema description coverage. The description only mentions 'using its unique identifier', which adds no meaning beyond the parameter name. The description does not compensate by explaining format, constraints, or valid values, leaving the agent to guess.

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 verb 'Get', the resource 'comprehensive metadata for a specific biological sample or dataset', and the method 'using its unique identifier'. It distinguishes from sibling search tools like search_by_name or search_by_type, which do not use a unique identifier.

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 clearly implies usage when a unique identifier is available and comprehensive metadata is needed. The context of sibling tools (search, query) provides implicit when-not-to-use guidance, but there is no explicit exclusion or alternative mentioned. This is clear context without exclusions.

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