build_pose_search_database_index

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

Annotations correctly cover that this is non-read-only and destructive. The description adds the async firing behavior and the wait_for_completion semantics (blocking with tick pumping), which is valuable context beyond annotations. However, it doesn't disclose that the existing index will be invalidated or replaced, which is important for a destructive operation.

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 two-sentence structure is front-loaded with the primary action and followed by the return format. The return list is somewhat verbose but clearly delineated.

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 no output schema, the description lists possible return fields but doesn't explain their types or meanings. For a destructive operation, it should mention that a rebuild invalidates or replaces the existing search index, which is crucial for an agent to understand.

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 coverage is 100%, so both parameters are fully documented in the schema. The description's return list partially overlaps with the parameters but adds no format or syntax details beyond what the schema provides.

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?

States a specific verb and resource: builds the PoseSearch index for a database. This is clearly distinguishable from siblings like add_animation_asset_to_pose_search_database or inspect_pose_search_database, which address different stages of the workflow.

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 when-to-use or when-not-to-use guidance. The agent isn't told that this should be run after modifying the database, or what conditions require a rebuild.

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