bc.get

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

No annotations are provided, so the description carries the full burden. It only mentions 'Get latest Biomedical Concept' without disclosing what 'latest' means, whether the conceptId must exist, what the return format is, or any error conditions. This is insufficient for a mutation-free lookup.

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 a single efficient sentence front-loading the key action. However, some additional context (like expected format of conceptId) could be added without making it verbose.

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 that there is only one parameter, no output schema, and no annotations, the description is too sparse. It omits necessary details such as what 'latest' means in context, whether the tool handles missing conceptIds, and what the response contains.

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, and the description only adds that the parameter is the 'conceptId' used to identify the concept. No format, constraints, or examples are provided, leaving the parameter's semantics largely underspecified.

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 'Biomedical Concept', and the selection mechanism 'by conceptId'. This provides a specific and unambiguous purpose that distinguishes it from sibling tools like 'bc.list' (likely lists all concepts) and 'bc.categories'.

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 implies usage when you need the latest version of a specific concept by its ID, but it does not explicitly state when to use this tool versus alternatives (e.g., when to use 'bc.list' versus 'bc.get') or provide any exclusions or prerequisites.

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