Neotoma

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose whether this is a mutation (implied by 'Register'), what permissions are needed, if it's idempotent, rate limits, or what happens on success/failure. For a tool with 7 parameters and no output schema, this is insufficient.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and includes essential scope information without unnecessary elaboration.

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 complexity (7 parameters, nested objects, no annotations, no output schema), the description is inadequate. It doesn't explain what 'Register' entails (e.g., creation vs. update), return values, error conditions, or interactions with sibling tools, leaving significant gaps for agent understanding.

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 43% (3 of 7 parameters have descriptions), which is low. The description adds minimal value by hinting at 'global and user-specific' scope, which relates to 'user_specific' and 'user_id' parameters, but doesn't explain key parameters like 'entity_type', 'schema_definition', or 'reducer_config' beyond what the schema provides. Baseline is 3 due to partial compensation.

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 ('Register') and resource ('schema or schema version'), and distinguishes scope ('global and user-specific'). However, it doesn't explicitly differentiate from sibling tools like 'update_schema_incremental' or 'analyze_schema_candidates', which would require a 5.

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?

No guidance on when to use this tool versus alternatives like 'update_schema_incremental' or 'store_structured'. The description mentions scope but doesn't provide explicit usage scenarios, prerequisites, or exclusions.

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