list_my_hives

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

With no annotations, the description carries the full burden. It implies a read-only operation via 'List' and adds context about local storage searching the current directory for .user_id files. However, it does not disclose potential edge cases like empty results, permissions, or side effects.

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 compact and front-loaded with the core purpose. The trigger list is somewhat long but not wasteful, and the sentence about local storage is useful. Overall, every sentence earns its place.

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?

For a simple list tool with no output schema, the description provides the essential return fields, trigger phrases, and local storage behavior. It is complete for most use cases, though it could mention what happens when no hives are found or when parameters are omitted.

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%, so the baseline is 3. The description adds a bit of context about local storage behavior, but the schema already describes both user_id (auto-detected) and project_path (for local storage), so no significant extra meaning is provided.

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 'List all project hives for a user', which is a specific verb-resource pair. It also specifies the return fields (project_id, project_name, entry count), distinguishing it from siblings like get_hive_overview or search_project.

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 explicit trigger phrases ('show me my hives', 'list my hives', etc.) that clearly signal when to use this tool. However, it does not mention alternatives or when not to use it, so it lacks the 'when-not' guidance for a 5.

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