Neotoma

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. It indicates this is a read operation ('List'), but doesn't cover permissions, rate limits, pagination behavior (despite limit/offset parameters), return format, or whether it's a filtered view versus comprehensive listing. For a tool with 3 parameters and no annotation coverage, this is inadequate.

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 maximally concise at 6 words with zero wasted language. It's front-loaded with the core purpose and efficiently structured as a single clear statement.

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 3 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools in the same domain, the description is incomplete. It provides basic purpose but lacks essential context about parameters, behavior, differentiation from siblings, and expected outputs that would be needed for effective tool selection and invocation.

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?

With 0% schema description coverage and 3 parameters (entity_id, limit, offset), the description provides no parameter semantics beyond implying entity_id is required ('for a given entity'). It doesn't explain what entity_id represents, what limit/offset do, or their expected formats. The description fails to compensate for the complete lack of schema documentation.

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 action ('List all observations') and target resource ('for a given entity'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling list tools like list_entity_types or list_relationships, which would require more specificity about what makes observations unique.

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 no guidance on when to use this tool versus alternatives. With multiple list/retrieve siblings (list_entity_types, list_relationships, retrieve_entities, retrieve_related_entities), there's no indication of when observations are appropriate versus other entity-related queries, nor any prerequisites or exclusions mentioned.

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