Neotoma

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 discloses that the tool returns health status and a count of stale snapshots, which is useful behavioral context. However, it lacks details on potential side effects (e.g., if 'auto_fix' is true, it may modify data), error conditions, or performance characteristics like rate limits. The description does not contradict any annotations, as none exist.

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 concise and front-loaded, consisting of two clear sentences that directly state the tool's purpose and output. There is no wasted verbiage or redundancy. However, it could be slightly more structured by explicitly separating the purpose from the output details, but this is minor.

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 tool's moderate complexity (involving snapshot health checks with an optional auto-fix parameter), no annotations, and no output schema, the description is partially complete. It covers the core purpose and output but lacks details on behavioral aspects like side effects, error handling, or example usage. It adequately informs basic use but leaves gaps for more advanced scenarios.

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 100%, with the single parameter 'auto_fix' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides (e.g., it does not explain the implications of setting 'auto_fix' to true). Given the high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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's purpose: to check for stale entity snapshots (specifically those with observation_count=0 but existing observations). It uses specific verbs ('check', 'returns') and identifies the resource ('entity snapshots'). However, it does not explicitly differentiate from sibling tools like 'retrieve_entity_snapshot' or 'list_observations', which could provide related but different functionality.

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. It does not mention prerequisites, such as needing existing snapshots or observations, or compare it to siblings like 'retrieve_entity_snapshot' for detailed snapshot info or 'list_observations' for observation data. Usage is implied only by the tool's name and purpose.

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